Triple
T1909580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas A&M bands |
E38077
|
entity |
| Predicate | studentParticipation |
P2434
|
FINISHED |
| Object | Texas A&M University students |
—
|
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: Texas A&M University students | Statement: [Texas A&M bands, studentParticipation, Texas A&M University students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentParticipation Context triple: [Texas A&M bands, studentParticipation, Texas A&M University students]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
C.
hasStudentEnrollment
Indicates that a person or entity is enrolled as a student in a particular course, program, or educational institution.
-
D.
studentSection
Indicates a relationship where a student is enrolled in or associated with a particular course section.
-
E.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.