Triple
T4673698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic salmon |
E103625
|
entity |
| Predicate | maximumTotalLength |
P56985
|
FINISHED |
| Object | about 150 centimeters |
—
|
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 150 centimeters | Statement: [Atlantic salmon, maximumTotalLength, about 150 centimeters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumTotalLength Context triple: [Atlantic salmon, maximumTotalLength, about 150 centimeters]
-
A.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
B.
maximumBodyLength
Indicates that there is an upper limit on the allowable length or size of a body (e.g., content, message, or object) in this relationship or action.
-
C.
hasMaximumLength
chosen
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
-
D.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
E.
maximumNumberOfSegments
Indicates the greatest allowable or observed count of discrete segments into which something can be or is divided.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.