Triple
T2393732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigres UANL |
E47599
|
entity |
| Predicate | typicalHomeAttendance |
P2636
|
FINISHED |
| Object | among highest in Liga MX |
—
|
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 Liga MX | Statement: [Tigres UANL, typicalHomeAttendance, among highest in Liga MX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHomeAttendance Context triple: [Tigres UANL, typicalHomeAttendance, among highest in Liga MX]
-
A.
attendance
chosen
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
D.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
E.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
- 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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc876d48881909e4d6f5ebe430012 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.