Triple
T6917194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lara Lettice Johnson-Wheeler |
E160089
|
entity |
| Predicate | hasPublicProfileAs |
P5387
|
FINISHED |
| Object | media personality |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: media personality | Statement: [Lara Lettice Johnson-Wheeler, hasPublicProfileAs, media personality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicProfileAs Context triple: [Lara Lettice Johnson-Wheeler, hasPublicProfileAs, media personality]
-
A.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
B.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
C.
publicProfile
chosen
Indicates that an entity’s profile or identifying information is visible and accessible to the general public.
-
D.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
E.
hasPublicPerception
Indicates that an entity is associated with a particular way it is viewed, judged, or regarded by the general public or society.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9e034cc81908f1e8f31b055e119 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.