Triple
T20518147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Seed |
E503732
|
entity |
| Predicate | hasDatabaseEntry |
P18283
|
FINISHED |
| Object | https://www.imdb.com/title/tt0708473/ |
—
|
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: https://www.imdb.com/title/tt0708473/ | Statement: [Space Seed, hasDatabaseEntry, https://www.imdb.com/title/tt0708473/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDatabaseEntry Context triple: [Space Seed, hasDatabaseEntry, https://www.imdb.com/title/tt0708473/]
-
A.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
B.
hasEntryOn
chosen
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
C.
hasEntryType
Indicates that something is associated with a specific category or type of entry within a system or dataset.
-
D.
hasTimedEntry
Indicates that an entity is associated with an entry or access that is constrained or defined by a specific time or time period.
-
E.
hasEntryFormula
Indicates that something is associated with a specific formula used to represent its entry or defining expression.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f43e0b08190b043f35645b264a0 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.