Triple
T1189193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xanadu |
E25317
|
entity |
| Predicate | mentionedInLine |
P831
|
FINISHED |
| Object | In Xanadu did Kubla Khan |
—
|
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: In Xanadu did Kubla Khan | Statement: [Xanadu, mentionedInLine, In Xanadu did Kubla Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionedInLine Context triple: [Xanadu, mentionedInLine, In Xanadu did Kubla Khan]
-
A.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
B.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
C.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
D.
usedInProductLine
Indicates that something (such as a component, material, or feature) is utilized within a particular product line.
-
E.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd57c3c481908bdca483fcaa3297 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.