Triple
T6878218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Five Stripes |
E158723
|
entity |
| Predicate | homeAttendanceReputation |
P2636
|
FINISHED |
| Object | among highest in MLS |
—
|
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: among highest in MLS | Statement: [The Five Stripes, homeAttendanceReputation, among highest in MLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAttendanceReputation Context triple: [The Five Stripes, homeAttendanceReputation, among highest in MLS]
-
A.
homeAtmosphereReputation
Indicates the perceived quality or character of the atmosphere or environment associated with a particular home.
-
B.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
attendancePromotion
Indicates a relationship where one entity promotes, encourages, or incentivizes attendance at an event, activity, or location for another entity.
-
D.
homeScore
Indicates the number of points or goals scored by the home team or home participant in a game or match.
-
E.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8e498bc81908b2fbe0c6a8b95b7 |
completed | March 27, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.