Triple
T27246963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tintin in Tibet |
E687370
|
entity |
| Predicate | continuityFollows |
P20918
|
FINISHED |
| Object | The Red Sea Sharks |
—
|
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 Red Sea Sharks | Statement: [Tintin in Tibet, continuityFollows, The Red Sea Sharks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityFollows Context triple: [Tintin in Tibet, continuityFollows, The Red Sea Sharks]
-
A.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
B.
continuedBy
chosen
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
C.
cultContinuity
Indicates the continuation or persistence of a religious cult’s practices, beliefs, or traditions over time.
-
D.
titleContinuity
Indicates that two works share a continuous or consistent use of the same title across versions, installments, or related contexts.
-
E.
belongsToContinuity
Indicates that something is part of, or exists within, a specific narrative or temporal continuity.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 10:42 a.m.