Triple
T27785338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Robert Chiltern |
E700944
|
entity |
| Predicate | pastAction |
P44556
|
FINISHED |
| Object | sold a Cabinet secret about the Suez Canal |
—
|
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: sold a Cabinet secret about the Suez Canal | Statement: [Sir Robert Chiltern, pastAction, sold a Cabinet secret about the Suez Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastAction Context triple: [Sir Robert Chiltern, pastAction, sold a Cabinet secret about the Suez Canal]
-
A.
pastMotion
Indicates that a motion or movement event occurred in the past relative to the reference time.
-
B.
usedInPast
Indicates that an entity has been utilized or employed at some point in the past, prior to the current time or context.
-
C.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
D.
pastOrdinary
chosen
Indicates that the related action or state occurred in the past using the simple (non-progressive, non-perfect) tense.
-
E.
usedInPastFor
Indicates that one entity was previously utilized for another entity or purpose in the past.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637d224c0819085f7af916d439d04 |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:24 p.m.