Triple
T33790772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | camphechlor |
E865924
|
entity |
| Predicate | wasFirstIntroduced |
P3297
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [camphechlor, wasFirstIntroduced, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstIntroduced Context triple: [camphechlor, wasFirstIntroduced, 1940s]
-
A.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
B.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
C.
introducedAsFirst
Indicates that one entity is presented or mentioned before any others in a given context or sequence.
-
D.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
-
E.
wasFirstProducedBy
Indicates that something (such as a product, work, or item) was initially created, manufactured, or brought into existence by a particular agent, organization, or producer.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.