Triple
T32292054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacDonald White Paper |
E824988
|
entity |
| Predicate | dividedLandIntoZonesForSales |
P18247
|
FINISHED |
| Object | A, B and C zones |
—
|
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: A, B and C zones | Statement: [MacDonald White Paper, dividedLandIntoZonesForSales, A, B and C zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dividedLandIntoZonesForSales Context triple: [MacDonald White Paper, dividedLandIntoZonesForSales, A, B and C zones]
-
A.
territorySold
Indicates that one entity has transferred ownership or control of a territory to another entity through a sale.
-
B.
partitionedTerritory
chosen
Indicates that a larger territory has been divided into distinct parts or regions, typically with defined boundaries or administrative separation.
-
C.
allocatesLandTo
Indicates that one party assigns or designates a portion of land for use or ownership by another party.
-
D.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
E.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd3500608190ba9e172c0458ff9f |
completed | May 3, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:44 a.m.