Triple
T4135953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanity Fair |
E85154
|
entity |
| Predicate | intendedUseLocation |
P21833
|
FINISHED |
| Object | home |
—
|
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: home | Statement: [Vanity Fair, intendedUseLocation, home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedUseLocation Context triple: [Vanity Fair, intendedUseLocation, home]
-
A.
typicalUseLocation
chosen
Indicates the usual or most common location where an entity is used or operates.
-
B.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
C.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.