Triple
T18179110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appendix Settlement |
E435235
|
entity |
| Predicate | typeOfLeaveAddressed |
P74490
|
FINISHED |
| Object | indefinite leave to remain |
—
|
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: indefinite leave to remain | Statement: [Appendix Settlement, typeOfLeaveAddressed, indefinite leave to remain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLeaveAddressed Context triple: [Appendix Settlement, typeOfLeaveAddressed, indefinite leave to remain]
-
A.
leaveType
chosen
Indicates the type or category of leave associated with an absence or time-off event (e.g., vacation, sick leave, parental leave).
-
B.
typeOfAddress
Indicates the specific category or kind of address (e.g., home, work, billing) associated with an entity.
-
C.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
D.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
E.
addressedFor
Indicates that something is directed, designated, or intended for a particular recipient or target.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dff9aad081909cc7eed2b64828f2 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.