Triple
T23165244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecuadorian exclusive economic zone |
E578694
|
entity |
| Predicate | resourceTypes |
P60481
|
FINISHED |
| Object | living resources |
—
|
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: living resources | Statement: [Ecuadorian exclusive economic zone, resourceTypes, living resources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceTypes Context triple: [Ecuadorian exclusive economic zone, resourceTypes, living resources]
-
A.
contributingResourceType
Indicates the type or category of a resource that contributes to or supports another resource or activity.
-
B.
resourceSystem
Indicates a relationship where one entity functions as or belongs to a system that manages, allocates, or organizes resources for another entity or context.
-
C.
sharesResourceType
Indicates that two or more entities use or are associated with the same type or category of resource.
-
D.
repositoryType
Indicates the kind or classification of a repository associated with an entity.
-
E.
primaryResourceType
chosen
Indicates the main or predominant type/category of resource associated with an entity or activity.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.