Triple
T1490451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C markup validation tools |
E29564
|
entity |
| Predicate | checks |
P26871
|
FINISHED |
| Object | syntax errors in markup |
—
|
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: syntax errors in markup | Statement: [W3C markup validation tools, checks, syntax errors in markup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checks Context triple: [W3C markup validation tools, checks, syntax errors in markup]
-
A.
checkedBy
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
B.
checksInformationFrom
chosen
Indicates that one entity verifies, reviews, or consults information originating from another entity.
-
C.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
D.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
E.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c233ec819087e1233af02aabfc |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.