Triple
T6094095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Eutrope |
E135834
|
entity |
| Predicate | traditionallyActiveInCentury |
P1560
|
FINISHED |
| Object | 3rd 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: 3rd century | Statement: [Saint Eutrope, traditionallyActiveInCentury, 3rd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyActiveInCentury Context triple: [Saint Eutrope, traditionallyActiveInCentury, 3rd century]
-
A.
activeInCentury
chosen
Indicates that an entity was active, influential, or operational during a specified century.
-
B.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
C.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
D.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
E.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9516ec819093e94ee8d3244e1b |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.