Triple
T30129244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montserrado |
E765785
|
entity |
| Predicate | formsPartOfShorelineNear |
P180802
|
FINISHED |
| Object | Monrovia |
—
|
NE NERFINISHED |
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: Monrovia | Statement: [Montserrado, formsPartOfShorelineNear, Monrovia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPartOfShorelineNear Context triple: [Montserrado, formsPartOfShorelineNear, Monrovia]
-
A.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
B.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
E.
hasHighwayAlongShore
Indicates that a highway runs adjacent to or closely follows the shoreline of a body of water.
- F. None of above. chosen
Provenance (4 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 29, 2026, 7:14 p.m.