Triple
T386700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal City |
E8794
|
entity |
| Predicate | developmentBegan |
P10779
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Crystal City, developmentBegan, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentBegan Context triple: [Crystal City, developmentBegan, 1960s]
-
A.
developedAt
Indicates the place or location where something was created, built, or developed.
-
B.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
E.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec447b5481908a5a084787b44ced |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea2dc3088190a2aeb4496aff3582 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.