Triple
T27678235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | yellow crazy ant |
E697836
|
entity |
| Predicate | notableImpactLocation |
P182734
|
FINISHED |
| Object | Christmas Island red crab populations |
—
|
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: Christmas Island red crab populations | Statement: [yellow crazy ant, notableImpactLocation, Christmas Island red crab populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableImpactLocation Context triple: [yellow crazy ant, notableImpactLocation, Christmas Island red crab populations]
-
A.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
B.
notableImpactCity
Indicates that an entity has had a significant or widely recognized impact on a particular city.
-
C.
notableImpactOn
chosen
Indicates that one entity has had a significant, recognizable, or influential effect on another entity.
-
D.
notableLocationFeatured
Indicates that a particular location is prominently highlighted or showcased in relation to the subject.
-
E.
notableLocationUse
Indicates that a location is notably used for a particular purpose, activity, or function associated with the subject.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: April 27, 2026, 2:45 p.m.