Triple
T29867416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gbXML |
E758493
|
entity |
| Predicate | hasSchemaDefinitionLanguage |
P37416
|
FINISHED |
| Object | XML Schema (XSD) |
—
|
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: XML Schema (XSD) | Statement: [gbXML, hasSchemaDefinitionLanguage, XML Schema (XSD)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchemaDefinitionLanguage Context triple: [gbXML, hasSchemaDefinitionLanguage, XML Schema (XSD)]
-
A.
hasSchemaLanguage
chosen
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
B.
isSchema
Indicates that one entity functions as the schema or structural definition governing the form, constraints, or organization of another entity.
-
C.
hasMetalanguage
Indicates that one entity serves as a metalanguage used to describe, define, or reason about another language or formal system.
-
D.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
E.
hasAxiomSchema
Indicates that one entity is associated with, defined by, or governed through a particular axiom schema.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 5:52 p.m.