Triple
T192809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML |
E3756
|
entity |
| Predicate | usesSyntaxElement |
P3097
|
FINISHED |
| Object | element |
—
|
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: element | Statement: [XML, usesSyntaxElement, element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSyntaxElement Context triple: [XML, usesSyntaxElement, element]
-
A.
usesElement
chosen
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.