Triple
T14530527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pheoby Watson |
E340899
|
entity |
| Predicate | functionInTheme |
P25955
|
FINISHED |
| Object | embodies female friendship |
—
|
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: embodies female friendship | Statement: [Pheoby Watson, functionInTheme, embodies female friendship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInTheme Context triple: [Pheoby Watson, functionInTheme, embodies female friendship]
-
A.
thematicFunction
Indicates how an entity participates in or contributes to the role structure of an event or situation (e.g., as agent, patient, instrument, etc.).
-
B.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
functionInText
Indicates that a text segment serves a specific rhetorical or structural function within a larger text.
-
D.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
E.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea052d01c81909c8592c351be6f35 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.