Triple
T8606997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morecambe F.C. |
E203822
|
entity |
| Predicate | homeTownType |
P83843
|
FINISHED |
| Object | seaside town |
—
|
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: seaside town | Statement: [Morecambe F.C., homeTownType, seaside town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTownType Context triple: [Morecambe F.C., homeTownType, seaside town]
-
A.
homeCityInStory
Indicates that a specified city serves as a character’s home city within the context of a particular story.
-
B.
nativeCity
Indicates that a city is the place where a person was born or is originally from.
-
C.
homeCityMetropolitanArea
Indicates that a specified city serves as the primary metropolitan area associated with a given entity’s home location.
-
D.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
-
E.
homeCitySince
Indicates the city that has served as an entity’s home starting from a specified point in time.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46eabe2c8190a2d13c353055a785 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.