Triple
T25310912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-SID |
E634603
|
entity |
| Predicate | identifierSpace |
P13658
|
FINISHED |
| Object | 24-bit service instance space |
—
|
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: 24-bit service instance space | Statement: [I-SID, identifierSpace, 24-bit service instance space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierSpace Context triple: [I-SID, identifierSpace, 24-bit service instance space]
-
A.
isSpaceSegmentOf
Indicates that one spatial region or segment is a constituent part or subdivision of a larger spatial extent or segment.
-
B.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
C.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
D.
namedSpace
chosen
Indicates that an entity has been assigned or is associated with a specific name within a particular namespace or naming context.
-
E.
baseSpacePreserved
Indicates that a mapping between fiber bundles preserves the underlying base space, leaving the base points unchanged.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939e84dc8190bef761d9bfee08a6 |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:26 p.m.