Triple
T32339626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Dog |
E826274
|
entity |
| Predicate | relativeSizeComparedToLittleDog |
P70596
|
FINISHED |
| Object | larger |
—
|
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: larger | Statement: [Big Dog, relativeSizeComparedToLittleDog, larger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeComparedToLittleDog Context triple: [Big Dog, relativeSizeComparedToLittleDog, larger]
-
A.
canineSize
chosen
Indicates the relative physical size or stature of a canine in comparison to other canines or a defined standard.
-
B.
canineSizeRelativeToApes
Indicates how the size of an entity’s canine teeth compares to those of apes, typically in relative or proportional terms.
-
C.
sizeRelativeToOtherLeopards
Indicates how an individual leopard’s size compares to that of other leopards.
-
D.
sizeRelativeToPikmin
Indicates how the size of an entity compares to that of a Pikmin, typically expressing whether it is smaller, similar, or larger relative to a Pikmin.
-
E.
relativeFruitSize
Indicates the comparative size relationship between one fruit and another (e.g., larger than, smaller than, or similar in 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:48 a.m.