Triple
T15451548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyndon Dykes |
E371661
|
entity |
| Predicate | choseToRepresent |
P118844
|
FINISHED |
| Object | Scotland at senior international level |
—
|
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: Scotland at senior international level | Statement: [Lyndon Dykes, choseToRepresent, Scotland at senior international level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choseToRepresent Context triple: [Lyndon Dykes, choseToRepresent, Scotland at senior international level]
-
A.
representativeDetermined
Indicates that an official representative has been identified and designated for a particular entity or context.
-
B.
representedFor
Indicates that one entity has acted or served as the official representative or proxy on behalf of another entity.
-
C.
eraRepresented
Indicates that a subject depicts, symbolizes, or stands for a particular historical or temporal era.
-
D.
partyRepresentation
Indicates that one party acts on behalf of, or serves as the representative of, another party in a given context or proceeding.
-
E.
hasRepresented
Indicates that one entity has acted or served as an official representative or agent for another entity.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03efaf82c81908b464e37ce9c159a |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:30 a.m.