Triple
T25910546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dasyurus |
E652879
|
entity |
| Predicate | belongsToInfraClass |
P12463
|
FINISHED |
| Object | Marsupialia |
—
|
NE NERFINISHED |
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: Marsupialia | Statement: [Dasyurus, belongsToInfraClass, Marsupialia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToInfraClass Context triple: [Dasyurus, belongsToInfraClass, Marsupialia]
-
A.
includesInfraclass
chosen
Indicates that one entity is classified as belonging to a specific infraclass within a taxonomic hierarchy.
-
B.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
C.
belongsToInfraorder
Indicates that one entity is taxonomically classified as a member of the infraorder specified by the other entity.
-
D.
containedInfrastructure
Indicates that one infrastructure element is physically or logically contained within another infrastructure element.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 22, 2026, 8:28 a.m.