Triple
T575999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTML5 |
E13761
|
entity |
| Predicate | removesElement |
P2360
|
FINISHED |
| Object | font |
—
|
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: font | Statement: [HTML5, removesElement, font]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesElement Context triple: [HTML5, removesElement, font]
-
A.
canBeRemovedBy
Indicates that one entity is capable of eliminating, detaching, or undoing another entity or its effect.
-
B.
removalMechanism
chosen
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
C.
removedFromCommandBy
Indicates that one entity was taken out of a position of command or authority by another entity.
-
D.
featureRemoved
Indicates that a previously existing feature has been taken out, disabled, or is no longer available.
-
E.
vanishesWhen
Indicates that one entity ceases to exist, be visible, or be present whenever a specified condition involving another entity holds.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b67395c8190a8046ff7debe9d1f |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.