Triple
T30261984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Texan Steak Ranch |
E769521
|
entity |
| Predicate | challengeIncludes |
P169724
|
FINISHED |
| Object | 72-ounce steak |
—
|
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: 72-ounce steak | Statement: [Big Texan Steak Ranch, challengeIncludes, 72-ounce steak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: challengeIncludes Context triple: [Big Texan Steak Ranch, challengeIncludes, 72-ounce steak]
-
A.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
B.
challengeUndertaken
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
C.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
D.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
E.
challengeFormat
Indicates that one entity specifies or defines the structure, rules, or format in which a challenge or contest is presented or conducted for another entity.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680a949c48190bd7c293ebad04cfb |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 7:42 p.m.