Triple
T30753071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpington chicken |
E783006
|
entity |
| Predicate | subsequentPopularVariety |
P170794
|
FINISHED |
| Object | Buff Orpington |
—
|
NE NERFINISHED |
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: Buff Orpington | Statement: [Orpington chicken, subsequentPopularVariety, Buff Orpington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentPopularVariety Context triple: [Orpington chicken, subsequentPopularVariety, Buff Orpington]
-
A.
subsequentlyPopularIn
Indicates that something became popular in a particular place, group, or context after an initial point in time or after another event.
-
B.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
C.
popular
Indicates that an entity is widely liked, admired, or favored by many people compared to alternatives.
-
D.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
E.
cultPopularFrom
Indicates that something has gained or exhibits cult popularity originating from a particular source, context, or group.
- F. None of above. chosen
Provenance (4 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:39 p.m.