Triple
T8945668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salmon |
E213215
|
entity |
| Predicate | maturesIn |
P86480
|
FINISHED |
| Object | ocean |
—
|
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: ocean | Statement: [Salmon, maturesIn, ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maturesIn Context triple: [Salmon, maturesIn, ocean]
-
A.
mustBeMaturedIn
Indicates that something is required to undergo a maturation process within a specified context, condition, or environment before it is considered ready or valid.
-
B.
maturityDuration
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
C.
maturityType
Indicates the kind or category of maturity associated with an entity, such as how or when an obligation, product, or process reaches its full or due state.
-
D.
maturity
Indicates that an entity has reached a specified stage of development, completeness, or readiness, often marking the point at which certain rights, obligations, or behaviors become applicable.
-
E.
hasMaturity
Indicates that an entity possesses a specified level, state, or stage of development or maturity.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66db998c8190999a7a686bbdda1f |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:59 p.m.