Triple
T8765410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCP |
E208326
|
entity |
| Predicate | standardIssueSince |
P3299
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [OCP, standardIssueSince, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardIssueSince Context triple: [OCP, standardIssueSince, 2019]
-
A.
standardIssueFor
Indicates that something is the typical or officially designated item or version provided for use in a particular context, role, or organization.
-
B.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
C.
standardizedSince
Indicates that something has been formally standardized starting from a specific point in time.
-
D.
becameStandardIssueByYear
chosen
Indicates that an item started being officially issued as standard equipment by a specified year.
-
E.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ee850b88190a0294bcbe4045aa3 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.