Triple
T33434547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARIA |
E856210
|
entity |
| Predicate | addsSemanticInformationTo |
P28757
|
FINISHED |
| Object | HTML |
—
|
NE NERFINISHED |
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: HTML | Statement: [ARIA, addsSemanticInformationTo, HTML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsSemanticInformationTo Context triple: [ARIA, addsSemanticInformationTo, HTML]
-
A.
hasSemanticsDefinedBy
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
hasSemantics
chosen
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with another entity.
-
C.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
-
D.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
E.
semanticType
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e483f0f48190b38bbb7d0d335c2e |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.