Triple
T21989815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML Infoset |
E543052
|
entity |
| Predicate | documentIdentifier |
P3247
|
FINISHED |
| Object | http://www.w3.org/TR/xml-infoset/ |
—
|
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: http://www.w3.org/TR/xml-infoset/ | Statement: [XML Infoset, documentIdentifier, http://www.w3.org/TR/xml-infoset/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentIdentifier Context triple: [XML Infoset, documentIdentifier, http://www.w3.org/TR/xml-infoset/]
-
A.
documentNumber
chosen
Indicates the unique identifying number assigned to a specific document in the relationship.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
recordIdentification
Indicates that an entity assigns or maintains a unique identifier or set of identifying information for a specific record.
-
D.
documentSource
Indicates that one entity serves as the origin, provider, or provenance source for a given document.
-
E.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.