Triple
T26161858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renfrewshire Cup |
E654131
|
entity |
| Predicate | hasLocalDerbyCharacter |
P71987
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Renfrewshire Cup, hasLocalDerbyCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalDerbyCharacter Context triple: [Renfrewshire Cup, hasLocalDerbyCharacter, true]
-
A.
hasLocalCommunityCharacter
Indicates that something possesses qualities or attributes typical of a specific local community or neighborhood.
-
B.
hasLocalCharacter
chosen
Indicates that something possesses qualities, features, or significance that are specific to a particular locality or region.
-
C.
hasDroidCharacter
Indicates that an entity features or includes a character that is a droid.
-
D.
hasDerbyName
Indicates that an entity is known by or uses a specific derby name, typically as an alternate or performance-related identity.
-
E.
hasDerbyStatus
Indicates that an entity holds a specific status or classification related to a derby event or competition.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 26, 2026, 8:30 p.m.