Triple
T15837929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwin III of Jerusalem |
E384029
|
entity |
| Predicate | tookFullPower |
P119848
|
FINISHED |
| Object | 1152 |
—
|
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: 1152 | Statement: [Baldwin III of Jerusalem, tookFullPower, 1152]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookFullPower Context triple: [Baldwin III of Jerusalem, tookFullPower, 1152]
-
A.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
-
D.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
-
E.
takesOver
Indicates that one entity assumes control, ownership, or responsibility for another entity, often replacing its previous controller.
- F. None of above. chosen
Provenance (4 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e3d48c8190ad0d0af89d062101 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.