Triple
T30105878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combine |
E765129
|
entity |
| Predicate | pioneeredIn |
P168453
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Combine, pioneeredIn, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pioneeredIn Context triple: [Combine, pioneeredIn, 1950s]
-
A.
pioneerOf
Indicates that an entity was among the first to develop, introduce, or significantly advance another entity, concept, or practice.
-
B.
pioneeringAspect
Indicates that something embodies an innovative, trailblazing, or first-of-its-kind quality within a particular domain or context.
-
C.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
D.
firstAnnouncedBy
Indicates that one entity is the original source or originator that publicly disclosed, reported, or made known another entity or item for the first time.
-
E.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67db9de4881908cb33939796ee8a2 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:09 p.m.