Triple
T16200315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganymede (mythology) |
E393180
|
entity |
| Predicate | grantedStatusByZeus |
P2246
|
FINISHED |
| Object | immortal |
—
|
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: immortal | Statement: [Ganymede (mythology), grantedStatusByZeus, immortal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedStatusByZeus Context triple: [Ganymede (mythology), grantedStatusByZeus, immortal]
-
A.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
B.
statusGrantedOn
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
C.
grantedBy
chosen
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
D.
grantedAs
Indicates that one entity is conferred, assigned, or bestowed in a particular role, status, or capacity to another entity.
-
E.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22709b0d88190b40787e0520d02ab |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.