Triple
T2175286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DocBook |
E48511
|
entity |
| Predicate | earlierVersionSyntax |
P22508
|
FINISHED |
| Object | DTD-based |
—
|
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: DTD-based | Statement: [DocBook, earlierVersionSyntax, DTD-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierVersionSyntax Context triple: [DocBook, earlierVersionSyntax, DTD-based]
-
A.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
B.
earlierVersionsSponsoredBy
Indicates that earlier versions of an item, work, or entity were financially or otherwise supported by a particular sponsor.
-
C.
backwardCompatibleWith
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
-
D.
predecessorVersion
chosen
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
E.
isFormallyAcceptedVersionOf
Indicates that one entity is the officially recognized or approved version of another, often superseding or formalizing an earlier or informal form.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.