Triple
T27941499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrison Hill |
E700760
|
entity |
| Predicate | communicatesOnlineWith |
P166471
|
FINISHED |
| Object | Rowena Price |
E700759
|
NE 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: Rowena Price | Statement: [Harrison Hill, communicatesOnlineWith, Rowena Price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesOnlineWith Context triple: [Harrison Hill, communicatesOnlineWith, Rowena Price]
-
A.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
B.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
C.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
D.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
E.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
- F. None of above. chosen
Provenance (5 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_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15c8f04f348190b01629d727c35dc3 |
completed | May 26, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 27, 2026, 7:18 p.m.