Triple
T7546072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchconnachan |
E178404
|
entity |
| Predicate | introducedSpecies |
P77921
|
FINISHED |
| Object | wallaby |
—
|
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: wallaby | Statement: [Inchconnachan, introducedSpecies, wallaby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedSpecies Context triple: [Inchconnachan, introducedSpecies, wallaby]
-
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.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
C.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
D.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
E.
introducedFromOldWorldToAmericas
Indicates that something was brought or transferred from the Old World (Europe, Africa, or Asia) to the Americas for the first time.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89963ec8190ae7b8a2b9508c074 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:48 p.m.