Triple
T33419739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Cirque (Las Vegas) |
E855813
|
entity |
| Predicate | parentProperty |
P32839
|
FINISHED |
| Object | Bellagio (Las Vegas) |
—
|
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: Bellagio (Las Vegas) | Statement: [Le Cirque (Las Vegas), parentProperty, Bellagio (Las Vegas)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentProperty Context triple: [Le Cirque (Las Vegas), parentProperty, Bellagio (Las Vegas)]
-
A.
parentType
Indicates that one entity serves as the direct parent or higher-level type from which another entity is derived or classified.
-
B.
ownedProperty
chosen
Indicates that one entity possesses legal ownership or control over another entity as property.
-
C.
targetProperty
Indicates that one entity serves as the intended goal, focus, or object of another entity’s action, influence, or effect.
-
D.
hierarchyProperty
Indicates a relationship where one property is defined as being above, below, or otherwise ordered relative to another property within a structured hierarchy.
-
E.
structureProperty
Indicates that one entity has a structural attribute, feature, or characteristic that describes how it is organized or composed.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:36 a.m.