Triple
T25631255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luisenstadt |
E642581
|
entity |
| Predicate | timeOfMajorGrowth |
P6451
|
FINISHED |
| Object | second half of the 19th century |
—
|
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: second half of the 19th century | Statement: [Luisenstadt, timeOfMajorGrowth, second half of the 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorGrowth Context triple: [Luisenstadt, timeOfMajorGrowth, second half of the 19th century]
-
A.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
B.
timePeriodOfMajorExpansion
chosen
Indicates the time span during which the referenced entity underwent its most significant growth or expansion.
-
C.
growthDuration
Indicates the length of time over which a growth process or development occurs.
-
D.
ageOfMajorMovement
Indicates the age at which a person experienced or participated in a major movement or significant social/political action.
-
E.
periodOfMajorRemains
Indicates the historical time period during which the primary surviving remains or artifacts associated with something were created or are dated.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 5:18 p.m.