Triple
T32450675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangrove Park on the Yakugachi River |
E829270
|
entity |
| Predicate | hasGuidedServices |
P53453
|
FINISHED |
| Object | guided nature tours |
—
|
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: guided nature tours | Statement: [Mangrove Park on the Yakugachi River, hasGuidedServices, guided nature tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuidedServices Context triple: [Mangrove Park on the Yakugachi River, hasGuidedServices, guided nature tours]
-
A.
isGuided
Indicates that one entity is being directed, led, or steered in its actions or movement by another entity or influence.
-
B.
hasGuides
chosen
Indicates that an entity is associated with one or more guides that provide direction, instruction, or assistance.
-
C.
isSelfGuided
Indicates that an entity operates, functions, or proceeds autonomously without direct external guidance or control.
-
D.
canBeGuidedTo
Indicates that one entity is capable of being directed, led, or steered toward another entity, state, or destination.
-
E.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c310edd08190a9f8e14056c45bd1 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.