Triple
T9313257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-root |
E224055
|
entity |
| Predicate | belongsToSetOf |
P56391
|
FINISHED |
| Object | thirteen root servers |
—
|
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: thirteen root servers | Statement: [L-root, belongsToSetOf, thirteen root servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSetOf Context triple: [L-root, belongsToSetOf, thirteen root servers]
-
A.
setsToOne
Indicates that an operation or condition forces a value, state, or variable to become exactly one.
-
B.
belongsToCycle
Indicates that an entity is part of, or contained within, a specific cycle or cyclic structure.
-
C.
associatedWithCollection
chosen
Indicates that an entity has a relationship or linkage to a particular collection, such as being included in, managed by, or contextually grouped with that collection.
-
D.
belongsToInteraction
Indicates that one entity is part of, or associated as a component within, a specific interaction event or process.
-
E.
belongsToForceType
Indicates that an entity is associated with, or classified under, a specific type of force.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.