Triple
T9746758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ladera Ranch, California |
E236329
|
entity |
| Predicate | developmentOpened |
P90474
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Ladera Ranch, California, developmentOpened, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentOpened Context triple: [Ladera Ranch, California, developmentOpened, 1999]
-
A.
developmentStart
Indicates the point in time or event when the development process of something begins.
-
B.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
developmentArc
Indicates the progression and transformation of something over time, typically outlining key stages of growth, change, or maturation within a broader narrative or process.
-
D.
developmentLinkedTo
Indicates that the development or progression of one entity is causally or contextually connected to the development or progression of another entity.
-
E.
developmentProject
Indicates a relationship where an organized effort or initiative is undertaken to plan, create, improve, or expand something over a defined period.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f677830819096d388b9c798ecd5 |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:23 p.m.