Triple
T25365940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lions |
E636098
|
entity |
| Predicate | isCollectiveName |
P1519
|
FINISHED |
| Object | team members |
—
|
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: team members | Statement: [The Lions, isCollectiveName, team members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCollectiveName Context triple: [The Lions, isCollectiveName, team members]
-
A.
usedCollectiveName
chosen
Indicates that a group of entities is referred to by a shared collective name.
-
B.
hasCollectiveCharacter
Indicates that a group or set of entities is treated as a unified whole, sharing a collective nature or identity rather than being considered solely as separate individuals.
-
C.
isCollectiveIdentityOf
Indicates that one entity functions as the shared or group-level identity that represents or encompasses another entity or set of entities.
-
D.
collectivelyKnownAs
Indicates that multiple entities are referred to together under a single shared name or designation.
-
E.
collectivityStatus
Indicates the state or condition of being part of a collective group versus being individual or separate.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10def5c81908f22e5a3c9f22af5 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:37 p.m.