Triple
T13534469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glebe Farm |
E323224
|
entity |
| Predicate | growthAreaRole |
P8652
|
FINISHED |
| Object | southern expansion of Cambridge |
—
|
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: southern expansion of Cambridge | Statement: [Glebe Farm, growthAreaRole, southern expansion of Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: growthAreaRole Context triple: [Glebe Farm, growthAreaRole, southern expansion of Cambridge]
-
A.
focusCityRole
Indicates that a city serves a particular primary role or function within a broader geographic or organizational context.
-
B.
assessmentAreaDefinedBy
Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
-
C.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
D.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
-
E.
expandsRoleOf
Indicates that one entity broadens, extends, or adds responsibilities to the role or function defined by 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbcad2881909fb7490311807f75 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.