Triple
T12955691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Foursquare |
E310004
|
entity |
| Predicate | typicalConstructionPeak |
P22153
|
FINISHED |
| Object | 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: 1900s | Statement: [American Foursquare, typicalConstructionPeak, 1900s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConstructionPeak Context triple: [American Foursquare, typicalConstructionPeak, 1900s]
-
A.
majorConstruction
Indicates a relationship where a construction project is large-scale, significant, or of primary importance in scope, impact, or resources.
-
B.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
C.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
D.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
E.
startOfConstructionApprox
Indicates that the construction of something began around an approximate or estimated point in time, rather than on a precisely known date.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:44 p.m.