Triple
T2032154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capra hircus |
E44540
|
entity |
| Predicate | FAORecognized |
P32410
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Capra hircus, FAORecognized, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FAORecognized Context triple: [Capra hircus, FAORecognized, yes]
-
A.
FAOStatus
chosen
Indicates the conservation or utilization status of an entity as defined by the Food and Agriculture Organization (FAO), such as its level of protection, endangerment, or management condition.
-
B.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
C.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
-
D.
resultRecognizedBy
Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
-
E.
recognizesText
Indicates that one entity detects and correctly identifies written or printed text present in or associated with 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.