Triple
T31738535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iberian wolf |
E810069
|
entity |
| Predicate | protectedStatusInPortugal |
P82432
|
FINISHED |
| Object | strictly protected |
—
|
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: strictly protected | Statement: [Iberian wolf, protectedStatusInPortugal, strictly protected]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedStatusInPortugal Context triple: [Iberian wolf, protectedStatusInPortugal, strictly protected]
-
A.
legalStatusInPortugal
chosen
Indicates the legal status or classification that an entity holds specifically within the jurisdiction of Portugal.
-
B.
limitedPortugalTo
Indicates that something is restricted in scope, effect, or applicability specifically to Portugal.
-
C.
roleInPortugal
Indicates that an entity holds or has held a specific role, position, or function within the context of Portugal.
-
D.
statusInBrazil
Indicates the legal, social, or operational status that an entity holds specifically within the context of Brazil.
-
E.
statusInSpain
Indicates the legal, social, or official condition or standing that an entity has within the jurisdiction of Spain.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 30, 2026, 11:24 p.m.