Triple
T12429115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wound Badge |
E296979
|
entity |
| Predicate | reintroductionDate |
P65312
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [Wound Badge, reintroductionDate, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintroductionDate Context triple: [Wound Badge, reintroductionDate, 1939]
-
A.
reintroducedSpecies
Indicates that a species has been brought back and established again in an area where it had previously disappeared or been extirpated.
-
B.
reintroducedInYear
chosen
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
C.
proposedReintroductionSite
Indicates that a location has been identified or suggested as a candidate site for reintroducing a species or population.
-
D.
reasonFor1995Reintroduction
Indicates the reason or motivation behind something being reintroduced in 1995.
-
E.
introducedSpecies
Indicates that a species has been brought by humans, intentionally or unintentionally, into an environment where it does not naturally occur.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.