Triple
T9901085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forteviot |
E182283
|
entity |
| Predicate | timeOfFlourishingAsRoyalCentre |
P29980
|
FINISHED |
| Object | 9th 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: 9th century | Statement: [Forteviot, timeOfFlourishingAsRoyalCentre, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFlourishingAsRoyalCentre Context triple: [Forteviot, timeOfFlourishingAsRoyalCentre, 9th century]
-
A.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
B.
flourishedIn
Indicates that an entity experienced its peak activity, success, or prominence 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.
flourishedToCentury
chosen
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
E.
flourishedAsPortToCentury
Indicates that a port city experienced its peak activity or prosperity as a port during a specified century.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e221448190b536742d1269f9d7 |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.