Triple
T23541797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mintonette |
E577771
|
entity |
| Predicate | teamsSeparatedBy |
P152737
|
FINISHED |
| Object | net |
—
|
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: net | Statement: [Mintonette, teamsSeparatedBy, net]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsSeparatedBy Context triple: [Mintonette, teamsSeparatedBy, net]
-
A.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
B.
teamsRepresent
Indicates that one or more teams act on behalf of, or serve as the official representatives of, a particular entity, organization, or group.
-
C.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
D.
teamRelationship
Indicates a collaborative or hierarchical association between entities functioning together as a team.
-
E.
divisionTeam2
Indicates that an entity is the second team participating in a particular division within a competition or organizational structure.
- 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_69e245f9d5d08190a4a20004e1784e20 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae1cb8b48190b51dd83b9fb116fe |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:10 p.m.