Triple
T16791050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphipoda |
E408109
|
entity |
| Predicate | largestKnownSize |
P72583
|
FINISHED |
| Object | about 34 centimetres in length |
—
|
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: about 34 centimetres in length | Statement: [Amphipoda, largestKnownSize, about 34 centimetres in length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largestKnownSize Context triple: [Amphipoda, largestKnownSize, about 34 centimetres in length]
-
A.
containsSomeOfLargestKnown
Indicates that an entity includes within it one or more items that rank among the largest known of their kind.
-
B.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
C.
largestKnownMembers
chosen
Indicates that the related entities are the largest known members within a specified group, category, or set.
-
D.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
E.
largestSpan
Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a5d10c8190a581de79e4f7ccfa |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.