Triple
T29817214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific |
E757142
|
entity |
| Predicate | wasIntroducedInEra |
P8259
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Pacific, wasIntroducedInEra, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIntroducedInEra Context triple: [Pacific, wasIntroducedInEra, early 20th century]
-
A.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
B.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
C.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
D.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
E.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f675642e3c819098f45ff76b60355f |
completed | May 2, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:27 p.m.