Triple
T5242372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Luxor |
E118373
|
entity |
| Predicate | pairWith |
P46528
|
FINISHED |
| Object | remaining obelisk at Luxor Temple |
—
|
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: remaining obelisk at Luxor Temple | Statement: [Obelisk of Luxor, pairWith, remaining obelisk at Luxor Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairWith Context triple: [Obelisk of Luxor, pairWith, remaining obelisk at Luxor Temple]
-
A.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
B.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
C.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
D.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
E.
isPairOf
chosen
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.