Triple
T10316107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scorpaena scrofa |
E242018
|
entity |
| Predicate | bodyLengthMax |
P56985
|
FINISHED |
| Object | 50 cm |
—
|
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: 50 cm | Statement: [Scorpaena scrofa, bodyLengthMax, 50 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyLengthMax Context triple: [Scorpaena scrofa, bodyLengthMax, 50 cm]
-
A.
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.
-
B.
memberOfBodySize
Indicates that one entity is a component or part whose size contributes to or characterizes the overall body size of another entity.
-
C.
maximumPayload
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
D.
fileNameLimit
Indicates a constraint or maximum allowed length or format for a file’s name in a given context.
-
E.
hasMaximumLength
chosen
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f4f354819080b4ed4bc61bdff6 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:49 a.m.