Triple
T4547424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postscript-1969 |
E110079
|
entity |
| Predicate | clarifiesTermUsage |
P5697
|
FINISHED |
| Object | paradigm as disciplinary matrix |
—
|
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: paradigm as disciplinary matrix | Statement: [Postscript-1969, clarifiesTermUsage, paradigm as disciplinary matrix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clarifiesTermUsage Context triple: [Postscript-1969, clarifiesTermUsage, paradigm as disciplinary matrix]
-
A.
terminologyNote
chosen
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
-
B.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
C.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57f11f648190b20892cca6f617b1 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.