Triple
T24848162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Léon Werth |
E621812
|
entity |
| Predicate | hasDedicationIn |
P62971
|
FINISHED |
| Object | The Little Prince |
—
|
NE NERFINISHED |
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 Little Prince | Statement: [Léon Werth, hasDedicationIn, The Little Prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDedicationIn Context triple: [Léon Werth, hasDedicationIn, The Little Prince]
-
A.
hasDedicationPurpose
Indicates that something is dedicated, devoted, or assigned to serve a particular purpose or function.
-
B.
dedicationBy
chosen
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
C.
dedicationStatus
Indicates the current state or condition of an entity’s dedication or commitment, such as whether it is active, pending, completed, or otherwise defined.
-
D.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
E.
usedAsDedicationFor
Indicates that something (such as a work, object, or act) is dedicated in honor of, or specifically intended for, another 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:20 a.m.