Triple
T31417516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Didn’t I See This Movie? |
E801430
|
entity |
| Predicate | numberType |
P153762
|
FINISHED |
| Object | solo number |
—
|
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: solo number | Statement: [Didn’t I See This Movie?, numberType, solo number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberType Context triple: [Didn’t I See This Movie?, numberType, solo number]
-
A.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
B.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
C.
digitType
Indicates the specific category or kind of digit (such as numerical, symbolic, or positional type) associated with an entity.
-
D.
singsNumberType
Indicates that an entity performs singing characterized by a specific type or category of number (e.g., musical number or song type).
-
E.
hasNumberType
chosen
Indicates that an entity is associated with a specific category or type of number (such as integer, float, or identifier format).
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: April 30, 2026, 8:45 p.m.