Triple
T9286621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sus philippensis |
E223407
|
entity |
| Predicate | isTerrestrial |
P85877
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sus philippensis, isTerrestrial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTerrestrial Context triple: [Sus philippensis, isTerrestrial, true]
-
A.
hasTerrestrialHabitat
chosen
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
-
B.
hasTerrestrialArea
Indicates that an entity possesses a specified extent of land area on the Earth's surface.
-
C.
containsTerrestrialMembers
Indicates that the set or group in question includes one or more members that live or occur on land (i.e., are terrestrial).
-
D.
terrestrialService
Indicates a service or operation that is provided on or relates specifically to land-based (earthbound) environments, as opposed to aerial, maritime, or space-based contexts.
-
E.
isLandPlant
Indicates that an entity is a plant that primarily lives and grows on land rather than in aquatic environments.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0821b1108190b16e9570b09a14de |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.