Triple
T23919139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Sua Ocean Trench |
E602166
|
entity |
| Predicate | hasEntryRegulation |
P34675
|
FINISHED |
| Object | visitors must pay local fee |
—
|
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: visitors must pay local fee | Statement: [To Sua Ocean Trench, hasEntryRegulation, visitors must pay local fee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryRegulation Context triple: [To Sua Ocean Trench, hasEntryRegulation, visitors must pay local fee]
-
A.
hasRegulations
chosen
Indicates that one entity imposes, contains, or is associated with rules or regulatory requirements that govern the behavior or operation of another entity.
-
B.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
C.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
D.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
E.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1600248190b38cfc93afb22a73 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:41 p.m.