Triple
T21989796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML Infoset |
E543052
|
entity |
| Predicate | informationItemType |
P66881
|
FINISHED |
| Object | document information item |
—
|
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: document information item | Statement: [XML Infoset, informationItemType, document information item]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationItemType Context triple: [XML Infoset, informationItemType, document information item]
-
A.
typeOfInformation
chosen
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
B.
informationCarrierType
Indicates the medium or format through which information is physically or digitally carried or delivered.
-
C.
ipoType
Indicates the type or category of an entity’s initial public offering (IPO) event.
-
D.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
E.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
- 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.