Triple
T37347444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renfrewshire South |
E927216
|
entity |
| Predicate | hasBeenRepresentedSince |
P12504
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Renfrewshire South, hasBeenRepresentedSince, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenRepresentedSince Context triple: [Renfrewshire South, hasBeenRepresentedSince, 2016]
-
A.
hasPreviousLongtimeRepresentative
Indicates that an entity was formerly represented for a long period by another specific representative.
-
B.
representedSince
chosen
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
-
C.
onceRepresentedBy
Indicates that an entity previously had another entity serving as its representative, but that representation is no longer current.
-
D.
laterRepresented
Indicates that one entity subsequently served as an official representative or agent for another entity at a later time.
-
E.
hasRepresented
Indicates that one entity has acted or served as an official representative or agent for another entity.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:16 p.m.