Triple
T12955693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Foursquare |
E310004
|
entity |
| Predicate | typicalConstructionEnd |
P107683
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [American Foursquare, typicalConstructionEnd, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalConstructionEnd Context triple: [American Foursquare, typicalConstructionEnd, 1930s]
-
A.
buildingEnd
Indicates the point or time at which the construction or existence of a building comes to a conclusion.
-
B.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
C.
monumentConstructionEnd
Indicates the date or time at which the construction of a monument was completed.
-
D.
endOfConstructionAttempt
Indicates the point at which a construction attempt is concluded, whether successfully completed, halted, or abandoned.
-
E.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
- 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_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. |
| PDg | Predicate description generation | batch_69d97e5811f481908178fac6d2e0efcd |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 5:44 p.m.