Triple
T28017400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mancini family |
E707584
|
entity |
| Predicate | hasCollectiveNickname |
P52939
|
FINISHED |
| Object | Mazarinettes |
—
|
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: Mazarinettes | Statement: [Mancini family, hasCollectiveNickname, Mazarinettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveNickname Context triple: [Mancini family, hasCollectiveNickname, Mazarinettes]
-
A.
usedCollectiveName
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.
collectivelyKnownAs
chosen
Indicates that multiple entities are referred to together under a single shared name or designation.
-
D.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
E.
collectiveNameForm
Indicates that one entity serves as the collective or group name form used to refer to multiple members of another entity or class.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: April 27, 2026, 8:07 p.m.