Triple
T28405218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of the Second French Empire |
E719507
|
entity |
| Predicate | startEventContext |
P24545
|
FINISHED |
| Object | proclamation of the Second French Empire |
—
|
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: proclamation of the Second French Empire | Statement: [Arms of the Second French Empire, startEventContext, proclamation of the Second French Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startEventContext Context triple: [Arms of the Second French Empire, startEventContext, proclamation of the Second French Empire]
-
A.
eventContext
Indicates the situational or background circumstances (such as time, place, conditions, or surrounding events) within which a particular event occurs or is interpreted.
-
B.
activityStartContext
chosen
Indicates the circumstances, conditions, or situation present at the moment an activity begins.
-
C.
serviceStartContext
Indicates the circumstances or conditions under which a service begins or is initiated.
-
D.
startTrigger
Indicates that one event, condition, or action initiates or causes the beginning of another.
-
E.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 1:23 a.m.