Triple
T13704348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln Island |
E328600
|
entity |
| Predicate | hasNearbyFeatures |
P2064
|
FINISHED |
| Object | other Paracel Islands reefs and islets |
—
|
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: other Paracel Islands reefs and islets | Statement: [Lincoln Island, hasNearbyFeatures, other Paracel Islands reefs and islets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFeatures Context triple: [Lincoln Island, hasNearbyFeatures, other Paracel Islands reefs and islets]
-
A.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
B.
nearbyFeature
chosen
Indicates that one entity is located close to or in the immediate vicinity of another entity.
-
C.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
D.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
E.
hasNearbyEventType
Indicates that an event of a specified type occurs in close spatial or contextual proximity to a given reference entity or location.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.