Triple
T1414525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falmouth Neck |
E31882
|
entity |
| Predicate | presentDayWithin |
P3475
|
FINISHED |
| Object | city of Portland, Maine |
—
|
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: city of Portland, Maine | Statement: [Falmouth Neck, presentDayWithin, city of Portland, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayWithin Context triple: [Falmouth Neck, presentDayWithin, city of Portland, Maine]
-
A.
partOfPresentDay
chosen
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
B.
presentOn
Indicates that one entity is physically located on the surface or within the bounds of another entity.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
contemporaryWith
Indicates that two entities existed, occurred, or were active during the same time period.
-
E.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e5f9d08190861206934cd71fd8 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.