Triple
T5417508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carry On Cleo |
E121166
|
entity |
| Predicate | featuresCharacterBasedOn |
P2004
|
FINISHED |
| Object | historical Cleopatra |
—
|
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: historical Cleopatra | Statement: [Carry On Cleo, featuresCharacterBasedOn, historical Cleopatra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCharacterBasedOn Context triple: [Carry On Cleo, featuresCharacterBasedOn, historical Cleopatra]
-
A.
characterBasedOn
chosen
Indicates that one character is modeled, inspired, or derived from another real or fictional entity.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created by another entity.
-
D.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
E.
influencesCharacter
Indicates that one entity affects, shapes, or alters the traits, behavior, or development of another entity’s character.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87e620f081909eb9a5e1f284e5a2 |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.