Triple
T3030856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fagasa |
E82889
|
entity |
| Predicate | nearbyProtectedAreas |
P28402
|
FINISHED |
| Object | rainforest-covered interior of Tutuila |
—
|
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: rainforest-covered interior of Tutuila | Statement: [Fagasa, nearbyProtectedAreas, rainforest-covered interior of Tutuila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyProtectedAreas Context triple: [Fagasa, nearbyProtectedAreas, rainforest-covered interior of Tutuila]
-
A.
hasNearbyNatureReserve
chosen
Indicates that one place or entity is located close to a designated nature reserve.
-
B.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
C.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
D.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
E.
situatedInProtectedArea
Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aee2fec81908116939a8d773fc4 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.