Triple
T4200689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaire ebolavirus |
E86056
|
entity |
| Predicate | firstIdentifiedIn |
P18472
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Zaire ebolavirus, firstIdentifiedIn, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIdentifiedIn Context triple: [Zaire ebolavirus, firstIdentifiedIn, 1976]
-
A.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
B.
firstDescribedAs
Indicates the original way or terms in which something was initially characterized, named, or documented.
-
C.
firstTestedBy
Indicates that an item, concept, or process was initially tested or tried out by a particular agent or entity.
-
D.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
E.
firstAppearedAt
chosen
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0363bbb8819093f396afe91972e2 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.