Triple
T4655649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guadalupe fur seal |
E102401
|
entity |
| Predicate | molt |
P19651
|
FINISHED |
| Object | annual molt on land |
—
|
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: annual molt on land | Statement: [Guadalupe fur seal, molt, annual molt on land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: molt Context triple: [Guadalupe fur seal, molt, annual molt on land]
-
A.
molting
chosen
Indicates the process by which an organism sheds and replaces an outer body covering, such as skin, feathers, or exoskeleton.
-
B.
mode
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
C.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
-
D.
pillar
Indicates that one entity serves as a fundamental support or central, stabilizing element for another entity or system.
-
E.
mouth
Indicates that one entity is the mouth (oral opening) of another entity, typically serving as the location for ingestion, speech, or related functions.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6317ba70819089145766d3462e57 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.