Triple
T26519568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foolish Wives |
E669914
|
entity |
| Predicate | studioBacklotUsed |
P7951
|
FINISHED |
| Object | Universal City, California |
—
|
NE NERFINISHED |
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: Universal City, California | Statement: [Foolish Wives, studioBacklotUsed, Universal City, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studioBacklotUsed Context triple: [Foolish Wives, studioBacklotUsed, Universal City, California]
-
A.
usedAsStudioBy
Indicates that a place or facility functions as a studio space utilized by a particular person or organization.
-
B.
hasBacklot
chosen
Indicates that one entity possesses or includes a backlot area associated with it.
-
C.
usedInProductionOfFilm
Indicates that something (such as a resource, tool, or material) was utilized during the making or production process of a film.
-
D.
filmStudioLot
Indicates a relationship where a film studio owns, operates, or is associated with a specific studio lot or production facility.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 1:26 a.m.