Triple
T19454499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenora Hills, California |
E486700
|
entity |
| Predicate | relocationDestinationOf |
P1660
|
FINISHED |
| Object | Eleven |
—
|
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: Eleven | Statement: [Lenora Hills, California, relocationDestinationOf, Eleven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationDestinationOf Context triple: [Lenora Hills, California, relocationDestinationOf, Eleven]
-
A.
laterRelocationDestination
Indicates that a location serves as the destination of a subsequent relocation event for an entity, occurring after an earlier move.
-
B.
relocationBy
Indicates that one entity causes or performs the movement or transfer of another entity from one location to another.
-
C.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
relocationAnnouncedBy
Indicates that the relocation of something (such as a person, organization, or asset) was publicly communicated or made known by a particular agent or source.
-
E.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c117ac8190a38c01c3191beaea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.