Triple
T30244560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ShUM cities |
E769019
|
entity |
| Predicate | timeOfGreatestFlourishing |
P15561
|
FINISHED |
| Object | 11th 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: 11th century | Statement: [ShUM cities, timeOfGreatestFlourishing, 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfGreatestFlourishing Context triple: [ShUM cities, timeOfGreatestFlourishing, 11th century]
-
A.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
B.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
C.
flourishedUnder
Indicates that one entity prospered, developed, or reached a peak of success under the influence, rule, guidance, or conditions provided by another entity.
-
D.
centuryOfGreatestInfluence
Indicates the century during which an entity exerted its greatest impact or influence.
-
E.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 7:39 p.m.