Triple
T90446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London |
E1817
|
entity |
| Predicate | hasAdministrativeUnit |
P3892
|
FINISHED |
| Object | London boroughs |
—
|
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: London boroughs | Statement: [London, hasAdministrativeUnit, London boroughs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeUnit Context triple: [London, hasAdministrativeUnit, London boroughs]
-
A.
hasAcademicUnit
Indicates that an entity is associated with, or belongs to, a specific academic unit such as a department, school, or faculty within an educational institution.
-
B.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
C.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
D.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
E.
parentOrganization
Indicates that one organization is the higher-level or owning entity in an organizational hierarchy relative to another organization.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24eb82d408190b0f9c786152e8e4c |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a24fed6b8c819080a6c0cd3b16e6bd |
completed | Feb. 28, 2026, 2:16 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.