Triple
T27572709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLNS |
E696075
|
entity |
| Predicate | definedInModel |
P178588
|
FINISHED |
| Object | OSI model |
—
|
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: OSI model | Statement: [CLNS, definedInModel, OSI model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInModel Context triple: [CLNS, definedInModel, OSI model]
-
A.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
B.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
definedInTerm
Indicates that one entity is defined or formally specified within the scope or content of a particular term.
-
D.
definedInPart
Indicates that something is specified, described, or formally established within a particular part or section of a larger whole.
-
E.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- F. None of above. chosen
Provenance (4 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 27, 2026, 1:44 p.m.