Triple
T5405284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenrothes |
E120876
|
entity |
| Predicate | hasPlannedNeighbourhoods |
P23364
|
FINISHED |
| Object | multiple residential precincts |
—
|
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: multiple residential precincts | Statement: [Glenrothes, hasPlannedNeighbourhoods, multiple residential precincts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedNeighbourhoods Context triple: [Glenrothes, hasPlannedNeighbourhoods, multiple residential precincts]
-
A.
hasPlannedCommunity
chosen
Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
-
B.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
hasNeighbourhoodStatus
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
D.
isPlannedCommunity
Indicates that a community has been intentionally designed and developed according to a coordinated plan rather than growing organically.
-
E.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8775e964819085c0ff5afea35f0e |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.