Triple
T30335461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumbarton F.C. |
E771605
|
entity |
| Predicate | originalGroundLocation |
P201869
|
FINISHED |
| Object | Dumbarton |
—
|
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: Dumbarton | Statement: [Dumbarton F.C., originalGroundLocation, Dumbarton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalGroundLocation Context triple: [Dumbarton F.C., originalGroundLocation, Dumbarton]
-
A.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
B.
originalStationLocation
Indicates the location where a station was initially established or first situated.
-
C.
firstKnownLocationOnEarth
Indicates the earliest known place on Earth where the entity was present, discovered, or recorded.
-
D.
originalLocationStatus
Indicates the status or condition of an entity’s original location, such as whether it remains, has changed, or is otherwise affected.
-
E.
originalLocationType
Indicates the type or category of the place where something was originally located or came from.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002dd4066c8190945a09ed82f44f3f |
completed | May 10, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_6a002b141f4081909999e14988105f3a |
completed | May 10, 2026, 6:52 a.m. |
| PDg | Predicate description generation | batch_6a002dd3294881909e860157fc459a85 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 29, 2026, 7:54 p.m.