Triple
T26373563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taxidea |
E660832
|
entity |
| Predicate | hasMemberWithBehavior |
P153407
|
FINISHED |
| Object | burrowing |
—
|
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: burrowing | Statement: [Taxidea, hasMemberWithBehavior, burrowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberWithBehavior Context triple: [Taxidea, hasMemberWithBehavior, burrowing]
-
A.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
B.
hasMemberCriteria
Indicates that a group, collection, or set is defined or constrained by specific criteria that its members must satisfy.
-
C.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
D.
hasMembersWith
chosen
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
E.
hasMemberWithIdentity
Indicates that a group or collection includes at least one member that possesses a specified identity or identifier.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 26, 2026, 11 p.m.