Triple
T9313272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-root |
E224055
|
entity |
| Predicate | dataServed |
P14669
|
FINISHED |
| Object | root zone file |
—
|
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: root zone file | Statement: [L-root, dataServed, root zone file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataServed Context triple: [L-root, dataServed, root zone file]
-
A.
dataReturned
Indicates that some data has been sent back or provided as a result of a request, query, or operation.
-
B.
dataAvailableFrom
Indicates that a specified source or provider offers access to certain data starting from a particular point or under certain conditions.
-
C.
dataPortal
chosen
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
dataCoverage
Indicates the extent or proportion of relevant data that is included, captured, or represented within a given dataset or system.
- 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.