Triple
T24847995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the king (The Little Prince) |
E621808
|
entity |
| Predicate | cannotSee |
P17604
|
FINISHED |
| Object | any subjects on his planet |
—
|
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: any subjects on his planet | Statement: [the king (The Little Prince), cannotSee, any subjects on his planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotSee Context triple: [the king (The Little Prince), cannotSee, any subjects on his planet]
-
A.
cannotShow
Indicates that one entity is unable or not permitted to display, reveal, or present another entity.
-
B.
cannot
chosen
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
C.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
D.
cannotTarget
Indicates that one entity is unable or not permitted to select or act upon another entity as a target.
-
E.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
- 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:20 a.m.