Triple
T30335462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumbarton F.C. |
E771605
|
entity |
| Predicate | hasBadgeFeature |
P182411
|
FINISHED |
| Object | Dumbarton Rock |
—
|
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 Rock | Statement: [Dumbarton F.C., hasBadgeFeature, Dumbarton Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBadgeFeature Context triple: [Dumbarton F.C., hasBadgeFeature, Dumbarton Rock]
-
A.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
-
B.
badgeVariesBy
Indicates that the characteristics or appearance of a badge change depending on some varying condition, context, or parameter.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
badgeUsage
Indicates how and in what context a badge is applied, displayed, or utilized in relation to an entity or activity.
-
E.
hasCrestBadge
Indicates that an entity possesses or is associated with a specific crest badge.
- 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_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 29, 2026, 7:54 p.m.