Triple
T529588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ali Hakim |
E10995
|
entity |
| Predicate | roleInPlot |
P11527
|
FINISHED |
| Object | suitor |
—
|
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: suitor | Statement: [Ali Hakim, roleInPlot, suitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPlot Context triple: [Ali Hakim, roleInPlot, suitor]
-
A.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
B.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d4984c8190ac372171b16bb5e4 |
completed | Feb. 28, 2026, 1:47 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.