Triple
T1320862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernley |
E28213
|
entity |
| Predicate | growthType |
P26502
|
FINISHED |
| Object | residential growth |
—
|
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: residential growth | Statement: [Fernley, growthType, residential growth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: growthType Context triple: [Fernley, growthType, residential growth]
-
A.
growthForm
Indicates the physical structure or habit in which something develops or grows (such as its overall shape, form, or growth pattern).
-
B.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
C.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
D.
growsIn
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
-
E.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
- F. None of above. chosen
Provenance (4 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19932888190a3d45871e84f112e |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf8158ac8190b8360ecccc2980bc |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:55 p.m.