Triple
T10647643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What's My Line? |
E250876
|
entity |
| Predicate | ruleElement |
P61392
|
FINISHED |
| Object | fixed number of allowed negative answers before game ended |
—
|
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: fixed number of allowed negative answers before game ended | Statement: [What's My Line?, ruleElement, fixed number of allowed negative answers before game ended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleElement Context triple: [What's My Line?, ruleElement, fixed number of allowed negative answers before game ended]
-
A.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
B.
ruleNumber
Indicates that an entity is associated with a specific rule identified by its number within a set of rules.
-
C.
policyElement
chosen
Indicates that something is a component or constituent part of a broader policy.
-
D.
styleOfRule
Indicates the stylistic or formatting convention that a particular rule follows or is expressed in.
-
E.
keyRule
Indicates that a rule or principle functions as a key or primary governing condition for something.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe29b8081908eb13637e0475ba1 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:05 p.m.