Triple
T36856799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardudhunera people |
E910817
|
entity |
| Predicate | hasRelationshipToSea |
P47434
|
FINISHED |
| Object | custodial responsibility for sea country |
—
|
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: custodial responsibility for sea country | Statement: [Mardudhunera people, hasRelationshipToSea, custodial responsibility for sea country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToSea Context triple: [Mardudhunera people, hasRelationshipToSea, custodial responsibility for sea country]
-
A.
touchesSea
Indicates that one entity is in direct physical contact with the sea or coastline of another entity.
-
B.
hasNotableSea
Indicates that an entity is associated with or contains a sea that is considered notable or significant.
-
C.
belongsToSea
Indicates that something is a part of, contained within, or naturally associated with a particular sea.
-
D.
associatedWithSea
chosen
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
E.
isPartOfSea
Indicates that one entity is a portion, region, or component contained within a larger sea.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.