Triple
T6955931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carol Peletier |
E161242
|
entity |
| Predicate | groupAffiliation |
P74283
|
FINISHED |
| Object | Atlanta survivor group |
—
|
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: Atlanta survivor group | Statement: [Carol Peletier, groupAffiliation, Atlanta survivor group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupAffiliation Context triple: [Carol Peletier, groupAffiliation, Atlanta survivor group]
-
A.
friendGroupRole
Indicates the specific role or function an individual holds within a particular friend group.
-
B.
ownerAffiliation
Indicates that an entity’s owner is formally associated with, belongs to, or is aligned with another entity or organization.
-
C.
affiliateOfType
Indicates that an affiliate entity belongs to, or is categorized under, a specific type or classification.
-
D.
airGroupRole
Indicates the specific function or duty an air group performs within a larger operation or organizational context.
-
E.
administrativeAffiliation
Indicates that one entity is formally connected to, governed by, or overseen by another entity within an administrative or organizational structure.
- F. None of above. chosen
Provenance (4 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacf8c8c8190a25dbacebeb4b66e |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dacb524c81909aade2282a4c0c01 |
completed | March 27, 2026, 7:30 p.m. |
Created at: March 27, 2026, 2:29 p.m.