Triple
T34398494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Morris |
E882902
|
entity |
| Predicate | sharesBackfieldWith |
P95842
|
FINISHED |
| Object | Larry Csonka |
—
|
NE NERFINISHED |
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: Larry Csonka | Statement: [Mercury Morris, sharesBackfieldWith, Larry Csonka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBackfieldWith Context triple: [Mercury Morris, sharesBackfieldWith, Larry Csonka]
-
A.
sharedBackfieldWith
chosen
Indicates that two players were part of the same offensive backfield unit on a team during overlapping time periods.
-
B.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
C.
sharesPlayerPoolWith
Indicates that two entities draw from or are associated with the same group or set of players.
-
D.
sharesArenaWith
Indicates that two entities use or occupy the same arena as a common venue or location.
-
E.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 1, 2026, 1:59 a.m.