Triple
T16442307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greensboro Swarm |
E399333
|
entity |
| Predicate | hasRosterSize |
P98624
|
FINISHED |
| Object | approximately 10–15 players |
—
|
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: approximately 10–15 players | Statement: [Greensboro Swarm, hasRosterSize, approximately 10–15 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRosterSize Context triple: [Greensboro Swarm, hasRosterSize, approximately 10–15 players]
-
A.
hasRosterSizeCategory
Indicates the classification of an entity based on the size of its roster or group of members.
-
B.
rosterSize
Indicates the total number of individuals included on a given roster.
-
C.
hasCurrentNumberOfMembers
Indicates the current count of members associated with a given entity.
-
D.
rosterSizeApprox
chosen
Indicates that the size of a group or roster is approximately equal to a specified number or range, allowing for minor variation.
-
E.
hasNetworkSize
Indicates the total number of nodes, members, or connections that make up a given network.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba91dc48190bc35db60f63d36d3 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.