Triple
T30289005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7482 |
E770319
|
entity |
| Predicate | definesPathSegment |
P193663
|
FINISHED |
| Object | domain |
—
|
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: domain | Statement: [RFC 7482, definesPathSegment, domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPathSegment Context triple: [RFC 7482, definesPathSegment, domain]
-
A.
routeSegment
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
B.
envisionedRouteSegment
Indicates a planned or imagined portion of a route that is conceptually defined but not yet realized or physically established.
-
C.
namespacePath
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming system.
-
D.
representsSegment
Indicates that one entity serves as a segment or portion of another, typically denoting that it forms a contiguous or logically bounded part within a larger whole.
-
E.
formsKeyPartOfRouteBetween
Indicates that something constitutes an essential segment or component of a route connecting two points or locations.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: April 29, 2026, 7:47 p.m.