Triple
T35381182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alene Lee |
E1022652
|
entity |
| Predicate | resistedPublicity |
P183079
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Alene Lee, resistedPublicity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resistedPublicity Context triple: [Alene Lee, resistedPublicity, true]
-
A.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
C.
hasPublicity
Indicates that an entity has received or is associated with public attention, promotion, or media exposure.
-
D.
resistedOrderTo
Indicates that one entity refused to comply with or actively opposed an order given by another entity.
-
E.
hasNotablePublicityReason
Indicates that an entity is associated with a specific reason or event that has led to notable public attention or publicity.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.