Triple
T27582366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISA bus |
E699614
|
entity |
| Predicate | commonInEra |
P117687
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [ISA bus, commonInEra, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInEra Context triple: [ISA bus, commonInEra, 1980s]
-
A.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
B.
chronologicalPeriodApprox
Indicates that one entity is associated with a time period that is approximately, but not exactly, the same as the time period of another entity.
-
C.
livedInEra
chosen
Indicates that an entity existed or was active during a particular historical era or time period.
-
D.
eraStartYearBC
Indicates the year (counting backward from year 1) in which a particular era or period begins, expressed in the BC (Before Christ/BCE) dating system.
-
E.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 2:03 p.m.