Triple
T12687542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenwood Avenue commercial blocks |
E303111
|
entity |
| Predicate | hasPrimaryPeriodOfDevelopment |
P53998
|
FINISHED |
| Object | early 1900s |
—
|
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: early 1900s | Statement: [Greenwood Avenue commercial blocks, hasPrimaryPeriodOfDevelopment, early 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryPeriodOfDevelopment Context triple: [Greenwood Avenue commercial blocks, hasPrimaryPeriodOfDevelopment, early 1900s]
-
A.
eraOfPrimaryDevelopment
chosen
Indicates the time period during which something was primarily developed or formed.
-
B.
hasTypicalBirthPeriod
Indicates the usual or characteristic time span during which the birth of an entity typically occurs.
-
C.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
-
D.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.