Triple
T37163816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBML |
E920742
|
entity |
| Predicate | schemaLanguage |
P37416
|
FINISHED |
| Object | EBML Schema |
—
|
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: EBML Schema | Statement: [EBML, schemaLanguage, EBML Schema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schemaLanguage Context triple: [EBML, schemaLanguage, EBML Schema]
-
A.
hasSchemaLanguage
chosen
Indicates that an entity uses, conforms to, or is defined in a particular schema language.
-
B.
constraintLanguage
Indicates that a specific formal language or syntax is used to express or define a constraint.
-
C.
dataModelLanguage
Indicates that one entity is a language or formalism used to define, describe, or structure the data model of another entity.
-
D.
schemaName
Indicates that an entity is associated with a particular schema by specifying the name of that schema.
-
E.
isSchema
Indicates that one entity functions as the schema or structural definition governing the form, constraints, or organization of another entity.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.