Triple
T18324889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Beja |
E438978
|
entity |
| Predicate | typicalCreationReason |
P5256
|
FINISHED |
| Object | grant to royal prince |
—
|
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: grant to royal prince | Statement: [Duke of Beja, typicalCreationReason, grant to royal prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCreationReason Context triple: [Duke of Beja, typicalCreationReason, grant to royal prince]
-
A.
reasonForCreation
chosen
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
B.
typicalActivationReason
Indicates the usual or most common reason why an entity, process, or condition becomes activated or triggered.
-
C.
typicalTrigger
Indicates that one entity commonly or characteristically causes, initiates, or brings about the occurrence of another entity or event.
-
D.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
E.
typicalCircumstance
Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aa93fb0819083293b80e8400c4e |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.