Triple
T481847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Common Golf |
E9184
|
entity |
| Predicate | teamStructure |
P12729
|
FINISHED |
| Object | multi-player roster |
—
|
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: multi-player roster | Statement: [Boston Common Golf, teamStructure, multi-player roster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamStructure Context triple: [Boston Common Golf, teamStructure, multi-player roster]
-
A.
personnelComposition
chosen
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
B.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
C.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f05a7f6c819082b4a5a3e69468a6 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.