Triple
T31793080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Behavioral Notion of Subtyping |
E811520
|
entity |
| Predicate | hasNamedPrinciple |
P99097
|
FINISHED |
| Object | Liskov Substitution Principle |
—
|
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: Liskov Substitution Principle | Statement: [A Behavioral Notion of Subtyping, hasNamedPrinciple, Liskov Substitution Principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamedPrinciple Context triple: [A Behavioral Notion of Subtyping, hasNamedPrinciple, Liskov Substitution Principle]
-
A.
hasPrincipleNamedAfter
chosen
Indicates that an entity has a principle, rule, or law that is named after a specified entity.
-
B.
hasPrincipleSet
Indicates that an entity is associated with or governed by a specific set of principles.
-
C.
hasPrincipleDefinition
Indicates that something serves as the primary or authoritative definition of a given concept or term.
-
D.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
-
E.
hasNamedForRole
Indicates that an entity has been given a specific name or label that corresponds to a particular role it plays.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 30, 2026, 11:39 p.m.