Triple
T9403346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-root |
E226527
|
entity |
| Predicate | belongsToRootServerLetters |
P88748
|
FINISHED |
| Object | A–M root server set |
—
|
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: A–M root server set | Statement: [H-root, belongsToRootServerLetters, A–M root server set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRootServerLetters Context triple: [H-root, belongsToRootServerLetters, A–M root server set]
-
A.
rootLetters
Indicates that one element specifies the fundamental root letters from which another linguistic form is derived.
-
B.
hasRootWord
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
C.
eachStanzaBeginsWithLetterOf
Indicates that every stanza in a text starts with a specific given letter.
-
D.
isRootOf
Indicates that one entity is the root or origin point from which another entity directly or indirectly descends or is derived.
-
E.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
- F. None of above. chosen
Provenance (4 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.