Triple
T36029261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Empire Hotel |
E1042212
|
entity |
| Predicate | hasNotableFictionalOwner |
P14482
|
FINISHED |
| Object | Chuck Bass |
E311591
|
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: Chuck Bass | Statement: [The Empire Hotel, hasNotableFictionalOwner, Chuck Bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFictionalOwner Context triple: [The Empire Hotel, hasNotableFictionalOwner, Chuck Bass]
-
A.
hasNotableFictionalBearer
Indicates that an entity is associated with at least one well-known fictional character that bears its name or designation.
-
B.
hasFictionalPet
Indicates that an entity has, owns, or is associated with a pet that is fictional or imaginary.
-
C.
hasFictionalProprietor
chosen
Indicates that something is owned, managed, or run by a fictional character or entity within a narrative context.
-
D.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
-
E.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
- 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_69f76e2c568881909e1e21f85252b0f0 |
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_6a396df2d7a08190a543304a8915f6c0 |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.