Triple
T18485354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirounga angustirostris |
E451674
|
entity |
| Predicate | femaleMaximumMass |
P131844
|
FINISHED |
| Object | up to about 600 to 800 kilograms |
—
|
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: up to about 600 to 800 kilograms | Statement: [Mirounga angustirostris, femaleMaximumMass, up to about 600 to 800 kilograms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: femaleMaximumMass Context triple: [Mirounga angustirostris, femaleMaximumMass, up to about 600 to 800 kilograms]
-
A.
maximumMaleBodyMass
Indicates the greatest recorded body mass among male individuals within a given group or species.
-
B.
maximumFemaleBodyLength
Indicates the greatest recorded length of the body for female individuals of a given entity or group.
-
C.
maximumRecordedMass
Indicates the greatest mass value that has been observed and recorded for an entity within a given context.
-
D.
maleBodyMass
Indicates that the relationship specifies the body mass or weight associated with a male individual.
-
E.
maximumMaleBodyLength
Indicates the greatest recorded body length measured for male individuals of a given entity or species.
- F. None of above. chosen
Provenance (4 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.