Triple
T11507553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-WNBA Second Team selection |
E272824
|
entity |
| Predicate | isTeamConstruct |
P99852
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [All-WNBA Second Team selection, isTeamConstruct, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamConstruct Context triple: [All-WNBA Second Team selection, isTeamConstruct, true]
-
A.
isTeamSpecific
Indicates that something applies only to, or is restricted to, a particular team rather than being general or shared across multiple teams.
-
B.
hasTeamStructure
Indicates that an entity is organized into, or associated with, a specific arrangement of teams or team hierarchy.
-
C.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
D.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
E.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db43a648190be859bec2fe9f43b |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.