Triple
T27358282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. E. Foster |
E685745
|
entity |
| Predicate | testDebutInnings |
P146829
|
FINISHED |
| Object | first innings |
—
|
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: first innings | Statement: [R. E. Foster, testDebutInnings, first innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testDebutInnings Context triple: [R. E. Foster, testDebutInnings, first innings]
-
A.
testDebutAgainst
Indicates that an entity’s first test appearance or performance occurs in opposition to, or is evaluated against, a specified counterpart or context.
-
B.
debutInTest
chosen
Indicates the event or context in which an entity makes its first official appearance or performance in a test setting.
-
C.
testDebut
Indicates the event or context in which an entity (such as a product, feature, or work) is first introduced or used in a testing environment.
-
D.
testDebutFor
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
E.
usesInnings
Indicates that one entity employs or incorporates another entity within the context or structure of innings (e.g., in a game, match, or statistical framework).
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c20321481908ba574ad96d93013 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:52 a.m.