Triple
T31623061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anguilla japonica |
E806946
|
entity |
| Predicate | juvenileForm |
P82364
|
FINISHED |
| Object | glass eel |
—
|
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: glass eel | Statement: [Anguilla japonica, juvenileForm, glass eel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: juvenileForm Context triple: [Anguilla japonica, juvenileForm, glass eel]
-
A.
hasJuvenileForm
chosen
Indicates that an entity possesses or exhibits a distinct juvenile or immature form in its life cycle.
-
B.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
C.
individualForm
Indicates that an entity is a specific, individual instance or form of something, distinguishing it from other forms or collective representations.
-
D.
hasJudgmentForm
Indicates that an entity is associated with, or expressed in, a particular formal structure or type of judgment (e.g., a specific logical or evaluative form).
-
E.
laterForms
Indicates that one entity is a subsequent or more recent form, version, or stage of another entity in a temporal or developmental sequence.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8afff6481909ece081c67160a08 |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:42 p.m.