Triple
T36233664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blyth Spartans A.F.C. |
E891315
|
entity |
| Predicate | hasBadgeTheme |
P182411
|
FINISHED |
| Object | Spartan warrior |
—
|
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: Spartan warrior | Statement: [Blyth Spartans A.F.C., hasBadgeTheme, Spartan warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBadgeTheme Context triple: [Blyth Spartans A.F.C., hasBadgeTheme, Spartan warrior]
-
A.
hasBadgeFeature
chosen
Indicates that one entity includes, supports, or is associated with a particular badge-related feature of another entity.
-
B.
hasBadgeSystem
Indicates that an entity includes or supports a badge-based system for recognizing or tracking achievements, statuses, or milestones.
-
C.
hasRankTheme
Indicates that one entity has a thematic role or subject matter characterized by a particular rank or hierarchical level.
-
D.
hasBadgeNumber
Indicates that an entity is associated with a specific badge identification number.
-
E.
usesSameBadgeAs
Indicates that two entities use an identical badge, implying they share the same badge identifier or physical badge for access or identification purposes.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.