Triple
T23517520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish |
E574404
|
entity |
| Predicate | appliesToCitizenshipOf |
P52511
|
FINISHED |
| Object | Scotland |
—
|
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: Scotland | Statement: [Scottish, appliesToCitizenshipOf, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToCitizenshipOf Context triple: [Scottish, appliesToCitizenshipOf, Scotland]
-
A.
appliesToCitizenshipStatus
chosen
Indicates that something (such as a rule, benefit, restriction, or condition) is relevant to or governs individuals based on their citizenship status.
-
B.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
C.
mayHoldCitizenshipOf
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
-
D.
isCitizenOf
Indicates that a person holds legal nationality or citizenship status in a particular country or state.
-
E.
impliesCitizenshipOrIdentity
Indicates that one entity’s status, attribute, or relationship entails or strongly suggests the citizenship or identity of 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa82a8448190bf7ad56137c5eb94 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.