Triple
T24847983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the king (The Little Prince) |
E621808
|
entity |
| Predicate | claimsToRule |
P32091
|
FINISHED |
| Object | the entire universe |
—
|
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: the entire universe | Statement: [the king (The Little Prince), claimsToRule, the entire universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToRule Context triple: [the king (The Little Prince), claimsToRule, the entire universe]
-
A.
claimsToBe
chosen
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
C.
claimsToFollow
Indicates that one entity asserts or professes adherence to the principles, rules, or leadership of another entity.
-
D.
claimsToDescribe
Indicates that one entity asserts that it provides an accurate or valid description of another entity or concept.
-
E.
claimsToEliminate
Indicates that one entity asserts it will remove, eradicate, or put an end to another entity or condition.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:20 a.m.