Triple
T30145336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP |
E766237
|
entity |
| Predicate | firstIntroducedAround |
—
|
GENERATED |
| Object | mid-1990s |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedAround Context triple: [ESP, firstIntroducedAround, mid-1990s]
-
A.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
B.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
-
C.
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.
-
D.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
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 (1 batch)
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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:18 p.m.