Triple
T8097950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Caesar |
E189032
|
entity |
| Predicate | groomedFor |
P2534
|
FINISHED |
| Object | succession to the Roman principate |
—
|
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: succession to the Roman principate | Statement: [Gaius Caesar, groomedFor, succession to the Roman principate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groomedFor Context triple: [Gaius Caesar, groomedFor, succession to the Roman principate]
-
A.
groomHouse
Indicates performing cleaning, organizing, or maintenance activities to keep a house neat and well-kept.
-
B.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
C.
groomingNeeds
Indicates the level, type, or frequency of grooming care required for an entity.
-
D.
preparedFor
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
E.
preparesFor
chosen
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4294b73481908c8373b8eca0f608 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.