Triple
T1427703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyre |
E30369
|
entity |
| Predicate | timePeriodOfFlourishing |
P15561
|
FINISHED |
| Object | 1st millennium BCE |
—
|
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: 1st millennium BCE | Statement: [Tyre, timePeriodOfFlourishing, 1st millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfFlourishing Context triple: [Tyre, timePeriodOfFlourishing, 1st millennium BCE]
-
A.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
B.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
C.
flourishedAfter
Indicates that one entity reached its peak or period of prosperity subsequent to the flourishing or peak period of another entity.
-
D.
historicalPeriodOfProsperity
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
E.
flourishedAmong
Indicates that an entity thrived, prospered, or reached a peak of development within a particular group, environment, or context.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.