Triple
T35666747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Family |
E1030586
|
entity |
| Predicate | locationOfFictionalUniverse |
P26457
|
FINISHED |
| Object | Los Angeles |
E715
|
NE 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: Los Angeles | Statement: [American Family, locationOfFictionalUniverse, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFictionalUniverse Context triple: [American Family, locationOfFictionalUniverse, Los Angeles]
-
A.
fictionalUniverseLocation
chosen
Indicates that one entity is a location or setting within the fictional universe to which the other entity belongs or in which it takes place.
-
B.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
C.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
D.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
E.
placeOfFictionalEvent
Indicates the location where a fictional event is depicted as occurring within a narrative or story.
- F. None of above.
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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4d26f1c8190860493ae43aa1323 |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.