Triple
T25264623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Wentworth |
E633397
|
entity |
| Predicate | isMetropolitan |
P20617
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Division of Wentworth, isMetropolitan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMetropolitan Context triple: [Division of Wentworth, isMetropolitan, true]
-
A.
isMetropolitanFor
Indicates that one entity serves as the primary metropolitan center or urban hub for another entity (such as a region, area, or service).
-
B.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
C.
isMetropolitanOf
Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
-
D.
isMetropolitanCoreOf
chosen
Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
-
E.
isCity
Indicates that the subject entity is classified as a city.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48396bf9481909012e4ed818abfbc |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:14 p.m.