Triple
T4930656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remover of Obstacles |
E110684
|
entity |
| Predicate | invokedAtTime |
P57350
|
FINISHED |
| Object | beginning of important tasks |
—
|
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: beginning of important tasks | Statement: [Remover of Obstacles, invokedAtTime, beginning of important tasks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedAtTime Context triple: [Remover of Obstacles, invokedAtTime, beginning of important tasks]
-
A.
servedTimeAt
Indicates the specific time period during which an entity was served or received service at a particular place or context.
-
B.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
C.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
-
D.
hasTimeOfAction
chosen
Indicates that an action is associated with a specific point or interval in time when it occurs.
-
E.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
- 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_69bd4415190c8190817bee7ec9f9f944 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.