Triple
T14262858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DS512 |
E353567
|
entity |
| Predicate | DSBDocumentSymbol |
P53404
|
FINISHED |
| Object | WT/DS512/R |
—
|
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: WT/DS512/R | Statement: [DS512, DSBDocumentSymbol, WT/DS512/R]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSBDocumentSymbol Context triple: [DS512, DSBDocumentSymbol, WT/DS512/R]
-
A.
hasDocumentSymbol
chosen
Indicates that an entity is associated with a particular document symbol or identifier used to reference that document.
-
B.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
-
C.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
D.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
-
E.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de63563fc88190b0abdbf8529c65eb |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.