Triple
T30753058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orpington chicken |
E783006
|
entity |
| Predicate | PCGBClass |
P111330
|
FINISHED |
| Object | heavy soft feather |
—
|
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: heavy soft feather | Statement: [Orpington chicken, PCGBClass, heavy soft feather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PCGBClass Context triple: [Orpington chicken, PCGBClass, heavy soft feather]
-
A.
structureClass
Indicates a classification relationship where an entity is assigned to or associated with a particular structural type or category.
-
B.
platformClass
Indicates the classification or category assigned to a platform, specifying what type or class of platform it is.
-
C.
crystalClass
Indicates the crystallographic symmetry class or system to which a crystal or mineral belongs.
-
D.
BIEClass
Indicates a classification relationship where an entity is assigned to or categorized under a specific BIE (Business Information Entity) class.
-
E.
clase
chosen
Indicates a classification or type relationship, where one entity is categorized as belonging to a particular class or category defined by 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f92c0448190a4c90ecfcbca0945 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.