Triple
T26373847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taxidea taxus |
E660838
|
entity |
| Predicate | legalStatusInSomeAreas |
P39644
|
FINISHED |
| Object | furbearer |
—
|
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: furbearer | Statement: [Taxidea taxus, legalStatusInSomeAreas, furbearer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInSomeAreas Context triple: [Taxidea taxus, legalStatusInSomeAreas, furbearer]
-
A.
legalStatusVariesBy
chosen
Indicates that the legal status of something differs depending on a specified jurisdiction, context, or set of conditions.
-
B.
legalStatusInMostCountries
Indicates the typical legal classification or treatment of something across the majority of countries.
-
C.
legalStatusInManyCountries
Indicates that the subject has a particular legal classification or standing that is recognized across numerous countries.
-
D.
legalStatusOfUnauthorizedAreas
Indicates the legal classification or regulatory standing that applies to areas considered unauthorized.
-
E.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 26, 2026, 11 p.m.