Triple
T9177207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buff Orpington |
E220230
|
entity |
| Predicate | isGoodFor |
P18991
|
FINISHED |
| Object | hatching and raising chicks |
—
|
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: hatching and raising chicks | Statement: [Buff Orpington, isGoodFor, hatching and raising chicks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGoodFor Context triple: [Buff Orpington, isGoodFor, hatching and raising chicks]
-
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.
isHouseholdStaple
Indicates that something is commonly and consistently kept on hand in a household as a basic, regularly used item.
-
D.
mayBeGivenTo
Indicates that something is permitted or eligible to be transferred, assigned, or provided from one entity to another.
-
E.
isEatenFor
Indicates that one entity is consumed as food for the benefit, nourishment, or use 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa60c3c8190b6335b9067de5b72 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.