Triple
T27938053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Lawrence Gordon |
E700663
|
entity |
| Predicate | familyThreatened |
P141945
|
FINISHED |
| Object | Alison Gordon |
—
|
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: Alison Gordon | Statement: [Dr. Lawrence Gordon, familyThreatened, Alison Gordon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyThreatened Context triple: [Dr. Lawrence Gordon, familyThreatened, Alison Gordon]
-
A.
threatensFamilyUnit
chosen
Indicates that one entity poses a danger or serious risk to the stability, safety, or integrity of another entity’s family unit.
-
B.
threatenedVictim
Indicates that one entity has issued or posed a threat of harm or adverse consequences toward another entity.
-
C.
familyAffectedBy
Indicates that one or more members of a person’s family experience or are impacted by a specified condition, event, or circumstance.
-
D.
threatsFaced
Indicates that an entity is exposed to or experiences specific dangers, risks, or harmful conditions.
-
E.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 7:15 p.m.