Triple
T27787982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lanner falcon |
E701008
|
entity |
| Predicate | falconryUse |
P163354
|
FINISHED |
| Object | traditional falconry in the Middle East |
—
|
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: traditional falconry in the Middle East | Statement: [lanner falcon, falconryUse, traditional falconry in the Middle East]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: falconryUse Context triple: [lanner falcon, falconryUse, traditional falconry in the Middle East]
-
A.
falconryUse
chosen
Indicates the use or practice of falconry involving one entity employing trained birds of prey for hunting or related activities with another entity.
-
B.
importanceInFalconry
Indicates the degree to which something holds significance, value, or centrality within the practice or context of falconry.
-
C.
huntingStyle
Indicates the characteristic manner or method an entity typically uses when hunting.
-
D.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
-
E.
hasWildlifeUse
Indicates that something is used by or provides a functional role for wildlife, such as habitat, food, shelter, or other ecological benefits.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:26 p.m.