Triple
T29868534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julii Caesares |
E758521
|
entity |
| Predicate | timeframeProminence |
P16254
|
FINISHED |
| Object | 2nd century BC |
—
|
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: 2nd century BC | Statement: [Julii Caesares, timeframeProminence, 2nd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeProminence Context triple: [Julii Caesares, timeframeProminence, 2nd century BC]
-
A.
timeSignificance
Indicates the degree to which a specific point or interval in time is important, impactful, or meaningful within a given context.
-
B.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
C.
timeframeRelative
Indicates a temporal relationship where one event, state, or condition is positioned in time relative to another (e.g., before, after, or overlapping).
-
D.
timePeriodOfMajorImportance
chosen
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
timePeriodInfluence
Indicates that one time period has an influence or shaping effect on another time period or on events occurring within it.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6768b2bf48190af4821d43d7ee766 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:52 p.m.