Triple
T10640114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arapaima gigas |
E250697
|
entity |
| Predicate | maximumReportedLength |
P23293
|
FINISHED |
| Object | over 300 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: over 300 cm | Statement: [Arapaima gigas, maximumReportedLength, over 300 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumReportedLength Context triple: [Arapaima gigas, maximumReportedLength, over 300 cm]
-
A.
maximumRecordedLength
chosen
Indicates the greatest length value that has been observed and recorded for the entity in question.
-
B.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
C.
maximumFileNameLength
Indicates the maximum number of characters allowed in a file name within a given system or context.
-
D.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
E.
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.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcbe5308190986bba438d19e852 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.