Triple
T2529243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisburg City Islanders |
E56114
|
entity |
| Predicate | playedAtLevel |
P39395
|
FINISHED |
| Object | third tier of U.S. soccer pyramid |
—
|
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: third tier of U.S. soccer pyramid | Statement: [Harrisburg City Islanders, playedAtLevel, third tier of U.S. soccer pyramid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedAtLevel Context triple: [Harrisburg City Islanders, playedAtLevel, third tier of U.S. soccer pyramid]
-
A.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
B.
playedOnCourse
Indicates that an entity (typically a player or team) participated in a game, match, or round that took place on a specific course.
-
C.
playedAfter
Indicates that one event, performance, or action occurred later in time than another.
-
D.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
E.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd25903f08190b46e12d32278daca |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd18e72a88190bdcf12b326d42fad |
completed | March 7, 2026, 7:19 a.m. |
Created at: March 6, 2026, 9:46 p.m.