Triple
T11603580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAME Studios |
E275192
|
entity |
| Predicate | movedToCurrentLocationIn |
P100553
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [FAME Studios, movedToCurrentLocationIn, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToCurrentLocationIn Context triple: [FAME Studios, movedToCurrentLocationIn, 1960s]
-
A.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
B.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
C.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
E.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d895502e0081909ee9c3d45d26cd91 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.