Triple
T16169950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | counterpart theory |
E392407
|
entity |
| Predicate | elaboratedInYear |
P121968
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [counterpart theory, elaboratedInYear, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elaboratedInYear Context triple: [counterpart theory, elaboratedInYear, 1986]
-
A.
statedInYear
Indicates that something was declared, expressed, or formally stated during a specific calendar year.
-
B.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
C.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
-
D.
articulatedInDocumentYear
Indicates that something is expressed, stated, or formally presented in a document created or associated with a specific year.
-
E.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb6de30819083af54b50ae5ae51 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.