Triple
T27583787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCL |
E699641
|
entity |
| Predicate | semanticsDefinedIn |
P74447
|
FINISHED |
| Object | OMG OCL specification |
—
|
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: OMG OCL specification | Statement: [OCL, semanticsDefinedIn, OMG OCL specification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticsDefinedIn Context triple: [OCL, semanticsDefinedIn, OMG OCL specification]
-
A.
hasSemanticsDefinedBy
chosen
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
-
C.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
definedInPart
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
E.
hasSemantics
Indicates that one entity carries or encodes the meaning, interpretation, or semantic content associated with 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63018926481908ab0101d087a7714 |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:03 p.m.