Triple
T9403339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-root |
E226527
|
entity |
| Predicate | servesRootZone |
P88747
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [H-root, servesRootZone, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRootZone Context triple: [H-root, servesRootZone, yes]
-
A.
servesRoute
Indicates that a service, vehicle, or provider operates along or provides transportation for a specified route.
-
B.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
-
C.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
-
D.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
E.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
- 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.