Triple
T1096402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XML Namespaces |
E24280
|
entity |
| Predicate | prefixBinding |
P7276
|
FINISHED |
| Object | association between a prefix and a namespace URI |
—
|
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: association between a prefix and a namespace URI | Statement: [XML Namespaces, prefixBinding, association between a prefix and a namespace URI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefixBinding Context triple: [XML Namespaces, prefixBinding, association between a prefix and a namespace URI]
-
A.
prefixAssignedBy
Indicates that a specific prefix has been designated or allocated to an entity by a particular assigning authority or agent.
-
B.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
C.
standardPrefix
chosen
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
D.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
E.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.