Triple
T14652833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eastern quoll |
E344030
|
entity |
| Predicate | introducedPredators |
P26652
|
FINISHED |
| Object | red fox |
—
|
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: red fox | Statement: [eastern quoll, introducedPredators, red fox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedPredators Context triple: [eastern quoll, introducedPredators, red fox]
-
A.
introducedSpecies
Indicates that a species has been brought by humans, intentionally or unintentionally, into an environment where it does not naturally occur.
-
B.
predators
chosen
Indicates a relationship where one organism hunts, kills, and consumes another organism as a food source.
-
C.
reintroducedSpecies
Indicates that a species has been brought back and established again in an area where it had previously disappeared or been extirpated.
-
D.
apexPredatorIn
Indicates that an entity is the top predator within a specified environment, ecosystem, or location, facing no regular natural predators there.
-
E.
mainPreySpecies
Indicates the species that serves as the primary prey or main food source for a given predator.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb517e7648190b9fc73d6cdbb68de |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.