Triple
T35293402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artaeum |
E1019289
|
entity |
| Predicate | timePeriodOfReturn |
P192249
|
FINISHED |
| Object | Second Era (during ESO events) |
—
|
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: Second Era (during ESO events) | Statement: [Artaeum, timePeriodOfReturn, Second Era (during ESO events)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfReturn Context triple: [Artaeum, timePeriodOfReturn, Second Era (during ESO events)]
-
A.
timeOfReturn
Indicates the specific time at which an entity comes back to a prior location or state.
-
B.
returnsAt
Indicates that an entity goes back to or comes again to a specified place, state, or context.
-
C.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
D.
rescissionPeriod
Indicates the time span during which a party is allowed to cancel or revoke an agreement or transaction without penalty.
-
E.
clearancePeriod
Indicates the span of time during which a particular authorization, permission, or clearance remains valid or in effect.
- F. None of above. chosen
Provenance (4 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:03 p.m.