Triple
T24328683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panther 21 trial |
E613174
|
entity |
| Predicate | hasDefendantCollectiveName |
P1519
|
FINISHED |
| Object | Panther 21 |
—
|
NE NERFINISHED |
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: Panther 21 | Statement: [Panther 21 trial, hasDefendantCollectiveName, Panther 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefendantCollectiveName Context triple: [Panther 21 trial, hasDefendantCollectiveName, Panther 21]
-
A.
hasDefendantAlternativeName
Indicates that an entity serving as a defendant is known or recorded under an alternative or additional 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.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
-
D.
usedCollectiveName
chosen
Indicates that a group of entities is referred to by a shared collective name.
-
E.
hasMainDefendant
Indicates that a legal case or proceeding identifies a specific individual or entity as its primary defendant.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ef86ec8190b27bc8cdff6c5c81 |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:54 a.m.