Triple
T8918194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celluloid |
E212344
|
entity |
| Predicate | hasPreferencesDialog |
P86389
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Celluloid, hasPreferencesDialog, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreferencesDialog Context triple: [Celluloid, hasPreferencesDialog, true]
-
A.
hasTypeOfPreference
Indicates that an entity holds a particular kind or category of preference toward something.
-
B.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
-
C.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
D.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
E.
allowsPreferenceVotes
Indicates that an entity permits the use of preference-based or ranked-choice voting in a given context.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66120eb08190913ab6c42f26ffb8 |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.