Triple
T31666268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latif Yahia |
E808132
|
entity |
| Predicate | allegedServiceFor |
P40226
|
FINISHED |
| Object | Uday Hussein |
—
|
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: Uday Hussein | Statement: [Latif Yahia, allegedServiceFor, Uday Hussein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedServiceFor Context triple: [Latif Yahia, allegedServiceFor, Uday Hussein]
-
A.
serviceFor
chosen
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
B.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
serviceFrom
Indicates that a service or transportation route originates from a specified source location or provider.
-
E.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 30, 2026, 10:59 p.m.