Triple
T662539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arbroath Smokies |
E11786
|
entity |
| Predicate | typicalLength |
P18065
|
FINISHED |
| Object | small to medium haddock |
—
|
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: small to medium haddock | Statement: [Arbroath Smokies, typicalLength, small to medium haddock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLength Context triple: [Arbroath Smokies, typicalLength, small to medium haddock]
-
A.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd081e8819097f289961f5eff29 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49ee356c0819085e2e82831cf1360 |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.