Triple
T10205016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cystoseira |
E242170
|
entity |
| Predicate | primaryProductionRole |
P37100
|
FINISHED |
| Object | primary producer |
—
|
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: primary producer | Statement: [Cystoseira, primaryProductionRole, primary producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProductionRole Context triple: [Cystoseira, primaryProductionRole, primary producer]
-
A.
primaryProducer
chosen
Indicates that an entity produces a good, service, or resource as the initial source in a supply, economic, or ecological chain.
-
B.
producerRole
Indicates that an entity serves in the role of producer for another entity, such as a work, product, or event.
-
C.
primaryRoleOnLine
Indicates that an entity serves as the main or most important role associated with a particular line (such as a transit line, product line, or communication line).
-
D.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
E.
hasProductionRole
Indicates that an entity holds a specific role or function in the production or creation process of another entity.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa22071c819095febd18dd607978 |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 10:37 a.m.