Triple
T6108376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xanadu (Citizen Kane) |
E136170
|
entity |
| Predicate | hasGateInscription |
P16756
|
FINISHED |
| Object | No Trespassing |
—
|
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: No Trespassing | Statement: [Xanadu (Citizen Kane), hasGateInscription, No Trespassing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGateInscription Context triple: [Xanadu (Citizen Kane), hasGateInscription, No Trespassing]
-
A.
hasInscriptions
chosen
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
C.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
D.
hasKeyPassage
Indicates that one entity contains or includes a particularly important or central passage relevant to another entity.
-
E.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b835ed48190971c3ba397ca329f |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.