Triple
T24847947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the rose (The Little Prince) |
E621807
|
entity |
| Predicate | isCaredForBy |
P52456
|
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: [the rose (The Little Prince), isCaredForBy, the little prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCaredForBy Context triple: [the rose (The Little Prince), isCaredForBy, the little prince]
-
A.
sitterOf
Indicates that one entity serves as a caretaker or babysitter responsible for looking after another entity.
-
B.
caregiverOf
chosen
Indicates a relationship where one entity provides ongoing care, support, or supervision for another entity’s well-being.
-
C.
associatedWithAnimal
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
-
D.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
-
E.
petOfNeighbor
Indicates that one entity is a pet belonging to, and typically living with, another entity who is a neighbor of the reference point.
- 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_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.