Triple
T18061239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chair H |
E432177
|
entity |
| Predicate | hasNeighborAfter |
P122642
|
FINISHED |
| Object | Chair I |
—
|
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: Chair I | Statement: [Chair H, hasNeighborAfter, Chair I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighborAfter Context triple: [Chair H, hasNeighborAfter, Chair I]
-
A.
hasNeighborCharacter
Indicates that one character is directly adjacent to another character in a sequence or arrangement.
-
B.
hasSubsequent
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
C.
neighboringBlockNext
Indicates that one block is directly adjacent to and immediately follows another block in the spatial or ordered layout.
-
D.
neighborElementNext
chosen
Indicates that one element is directly adjacent to and immediately follows another element in a sequence or structure.
-
E.
hasNorthNeighbor
Indicates that one entity is located directly to the north of 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c1066f508190bacf1122e366f87b |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.