Triple
T5903750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title Conditions (Scotland) Act 2003 |
E131288
|
entity |
| Predicate | typeOfTitleCondition |
P66834
|
FINISHED |
| Object | real burden |
—
|
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: real burden | Statement: [Title Conditions (Scotland) Act 2003, typeOfTitleCondition, real burden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTitleCondition Context triple: [Title Conditions (Scotland) Act 2003, typeOfTitleCondition, real burden]
-
A.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
B.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
C.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
D.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:58 p.m.