Triple
T8952274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Wyandotte |
E213380
|
entity |
| Predicate | hasStandardSizeVariant |
P455
|
FINISHED |
| Object | large fowl |
—
|
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: large fowl | Statement: [Black Wyandotte, hasStandardSizeVariant, large fowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardSizeVariant Context triple: [Black Wyandotte, hasStandardSizeVariant, large fowl]
-
A.
hasStandardizedDimensions
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
-
B.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
C.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
D.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
E.
availableInSize
Indicates that something is offered or can be obtained in a particular size.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.