Triple
T9314303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | youth offending teams |
E224079
|
entity |
| Predicate | statutoryPartner |
P68813
|
FINISHED |
| Object | local authority |
—
|
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: local authority | Statement: [youth offending teams, statutoryPartner, local authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statutoryPartner Context triple: [youth offending teams, statutoryPartner, local authority]
-
A.
lawPartnerOf
Indicates a professional relationship in which two individuals are partners in the same law firm or legal practice.
-
B.
symbolicPartnerOf
Indicates a relationship in which two entities are formally or representationally associated as partners in a symbolic, rather than practical or operational, sense.
-
C.
statePartner
chosen
Indicates that two entities are formally partnered or allied at the level of state or governmental institutions.
-
D.
judicialPartner
Indicates a formal partnership or collaborative relationship between entities within a judicial or court-related context.
-
E.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.