Triple
T17588072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner London Education Authority |
E428375
|
entity |
| Predicate | hasPolicyOn |
P126667
|
FINISHED |
| Object | school admissions in Inner London |
—
|
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: school admissions in Inner London | Statement: [Inner London Education Authority, hasPolicyOn, school admissions in Inner London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyOn Context triple: [Inner London Education Authority, hasPolicyOn, school admissions in Inner London]
-
A.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within it.
-
B.
hasPolicyStatus
Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
-
C.
appliesPolicyOn
chosen
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
D.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
E.
isOnPolicy
Indicates that an action, configuration, or behavior complies with and adheres to a specified policy or set of rules.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e50a80819098920d9190c30225 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.