Triple
T29619775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monhegan Island, Maine |
E754962
|
entity |
| Predicate | noFeature |
P167517
|
FINISHED |
| Object | no bridge connection to mainland |
—
|
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: no bridge connection to mainland | Statement: [Monhegan Island, Maine, noFeature, no bridge connection to mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noFeature Context triple: [Monhegan Island, Maine, noFeature, no bridge connection to mainland]
-
A.
nonTriggerFeature
Indicates that a feature or characteristic is present but does not initiate, cause, or trigger the associated event, process, or condition.
-
B.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
C.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
D.
lessFeatureRichThan
Indicates that one entity has fewer or less advanced features or capabilities than another entity.
-
E.
noOption
Indicates that no valid or applicable option is available or selected in the given context.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e24430081908f8731d6f52e0a2c |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:33 p.m.