Triple
T28326125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Township of Scarborough |
E717413
|
entity |
| Predicate | primaryLandUseEarly |
P14072
|
FINISHED |
| Object | agricultural |
—
|
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: agricultural | Statement: [Township of Scarborough, primaryLandUseEarly, agricultural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLandUseEarly Context triple: [Township of Scarborough, primaryLandUseEarly, agricultural]
-
A.
primaryLandUse
chosen
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
B.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
C.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
D.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
E.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
Created at: April 28, 2026, 12:28 a.m.