Triple
T10176472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuckoo Orpington |
E235864
|
entity |
| Predicate | isSuitedFor |
P18991
|
FINISHED |
| Object | temperate climates |
—
|
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: temperate climates | Statement: [Cuckoo Orpington, isSuitedFor, temperate climates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuitedFor Context triple: [Cuckoo Orpington, isSuitedFor, temperate climates]
-
A.
isSuitableFor
chosen
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
B.
lessSuitableFor
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
C.
isAbout
Indicates that one entity has as its subject, focus, or primary concern the content, topic, or theme represented by another entity.
-
D.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
E.
qualifiesFrom
Indicates that one entity gains an official status, capability, or eligibility as a result of successfully completing or meeting the requirements of 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdecd3a2688190bce277bffffcbf8b |
completed | April 2, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:11 p.m.