Triple
T29730575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Barrasso |
E752307
|
entity |
| Predicate | playedDirectlyFrom |
P179815
|
FINISHED |
| Object | high school |
—
|
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: high school | Statement: [Tom Barrasso, playedDirectlyFrom, high school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedDirectlyFrom Context triple: [Tom Barrasso, playedDirectlyFrom, high school]
-
A.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
B.
playedWhile
Indicates that one activity or event occurred concurrently with another, with the second serving as the temporal context during which the first was performed.
-
C.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
D.
playedProfessionalFrom
Indicates that an individual played professional-level sports for a particular team or organization starting from a specified time.
-
E.
playsWithin
Indicates that one entity performs or takes place inside the spatial or temporal bounds of 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 28, 2026, 7:42 p.m.