Triple
T13407980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | largemouth bass |
E320010
|
entity |
| Predicate | mouthCharacteristic |
P109792
|
FINISHED |
| Object | upper jaw extends past the eye |
—
|
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: upper jaw extends past the eye | Statement: [largemouth bass, mouthCharacteristic, upper jaw extends past the eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthCharacteristic Context triple: [largemouth bass, mouthCharacteristic, upper jaw extends past the eye]
-
A.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
-
B.
mouthColor
Indicates the color attribute associated specifically with an entity’s mouth.
-
C.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
-
D.
mouthNear
Indicates that one entity’s mouth is positioned close to another entity or object in space.
-
E.
mouthDirection
Indicates the orientation or facing direction of a mouth relative to a reference frame or another object.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbae4d2c5481908facfaaa1501e344 |
completed | April 12, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:35 p.m.