Triple
T7946519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ying |
E184510
|
entity |
| Predicate | flourishedDuringCentury |
P15561
|
FINISHED |
| Object | 5th century 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: 5th century BCE | Statement: [Ying, flourishedDuringCentury, 5th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flourishedDuringCentury Context triple: [Ying, flourishedDuringCentury, 5th century BCE]
-
A.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
B.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
C.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
discoveredInCentury
Indicates that an entity was discovered during a specific 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b29a570819091a2ac185a8d57c4 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.