Triple
T28673230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmasland |
E725784
|
entity |
| Predicate | controlledThrough |
P49579
|
FINISHED |
| Object | Charlie Manx’s will |
—
|
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: Charlie Manx’s will | Statement: [Christmasland, controlledThrough, Charlie Manx’s will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledThrough Context triple: [Christmasland, controlledThrough, Charlie Manx’s will]
-
A.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
B.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
C.
controlledFor
Indicates that the influence or effect of a specified factor has been accounted for or neutralized when assessing the relationship between other variables or entities.
-
D.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
E.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 28, 2026, 5:05 a.m.