Triple
T62169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | golden eagle |
E1234
|
entity |
| Predicate | protectedStatus |
P1359
|
FINISHED |
| Object | protected in many range countries |
—
|
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: protected in many range countries | Statement: [golden eagle, protectedStatus, protected in many range countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedStatus Context triple: [golden eagle, protectedStatus, protected in many range countries]
-
A.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
B.
protectedIn
chosen
Indicates that one entity is safeguarded, preserved, or kept safe within the context, environment, or jurisdiction of another entity.
-
C.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.