Triple
T30338747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Object Data Manager |
E771690
|
entity |
| Predicate | schemaDefinedBy |
P152925
|
FINISHED |
| Object | ODM class definitions |
—
|
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: ODM class definitions | Statement: [Object Data Manager, schemaDefinedBy, ODM class definitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schemaDefinedBy Context triple: [Object Data Manager, schemaDefinedBy, ODM class definitions]
-
A.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
B.
schemaName
Indicates that an entity is associated with a particular schema by specifying the name of that schema.
-
C.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
-
D.
wasDefinedBy
chosen
Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
-
E.
schemeType
Indicates the classification or category of a scheme that an entity is associated with or operates under.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681cf69588190b1a6373ddf29dd6a |
completed | May 2, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:55 p.m.