Triple
T11941418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Impossible Voyage |
E284185
|
entity |
| Predicate | hasStarFilmCatalogueNumber |
P102268
|
FINISHED |
| Object | 641–659 |
—
|
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: 641–659 | Statement: [The Impossible Voyage, hasStarFilmCatalogueNumber, 641–659]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarFilmCatalogueNumber Context triple: [The Impossible Voyage, hasStarFilmCatalogueNumber, 641–659]
-
A.
hasPicardNumber
Indicates that an entity (typically an algebraic variety) has a specified Picard number, i.e., the rank of its Picard group.
-
B.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
C.
isPrimaryStarOf
Indicates that a star serves as the main or central stellar object in relation to a specified system, object, or context.
-
D.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
-
E.
hasIMDbId
Indicates that an entity is associated with a specific identifier used by the Internet Movie Database (IMDb) to uniquely reference it.
- F. None of above. chosen
Provenance (4 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90342bb908190a019ac91a2b82f3d |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.