Triple
T3418656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simula |
E72066
|
entity |
| Predicate | hasParadigm |
P11868
|
FINISHED |
| Object | object-oriented |
—
|
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: object-oriented | Statement: [Simula, hasParadigm, object-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParadigm Context triple: [Simula, hasParadigm, object-oriented]
-
A.
supportedParadigm
chosen
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
B.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
-
C.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
D.
hasDistinctiveFrameworkWith
Indicates that one entity possesses a unique or distinguishing structural framework in relation to another entity.
-
E.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
- 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92df1e48190bbf22a47e44579f1 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.