Triple
T28050279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Section of Tokyo Stock Exchange |
E708800
|
entity |
| Predicate | relativeToOtherSections |
P23578
|
FINISHED |
| Object | higher than Second Section |
—
|
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: higher than Second Section | Statement: [First Section of Tokyo Stock Exchange, relativeToOtherSections, higher than Second Section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToOtherSections Context triple: [First Section of Tokyo Stock Exchange, relativeToOtherSections, higher than Second Section]
-
A.
relocatedSection
Indicates that a section has been moved from its original location to a new location within a structure or document.
-
B.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
linedSections
Indicates that one section is arranged or positioned in alignment with another section.
-
E.
appliesToSectionOf
Indicates that something is relevant or applicable specifically to a particular section or subsection of a larger whole.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: April 27, 2026, 8:32 p.m.