Triple
T9313121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-root |
E224051
|
entity |
| Predicate | underliesService |
P4501
|
FINISHED |
| Object | Internet domain name resolution |
—
|
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: Internet domain name resolution | Statement: [F-root, underliesService, Internet domain name resolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underliesService Context triple: [F-root, underliesService, Internet domain name resolution]
-
A.
serviceUnder
Indicates that one entity operates, functions, or is provided under the authority, management, or jurisdiction of another entity.
-
B.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
C.
underlies
chosen
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
D.
underlyingCompanyService
Indicates that one entity functions as a foundational or supporting service for another company or business entity.
-
E.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
- 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.