Triple
T25770972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles II of Anjou |
E649017
|
entity |
| Predicate | retainedControlOf |
P50835
|
FINISHED |
| Object | mainland Kingdom of Naples |
—
|
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: mainland Kingdom of Naples | Statement: [Charles II of Anjou, retainedControlOf, mainland Kingdom of Naples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainedControlOf Context triple: [Charles II of Anjou, retainedControlOf, mainland Kingdom of Naples]
-
A.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
B.
continuesToControl
chosen
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
C.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of another entity.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf84fb88190b40280340332743e |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:29 a.m.