Triple
T35924352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nermal |
E1038978
|
entity |
| Predicate | oftenSentTo |
P64532
|
FINISHED |
| Object | Abu Dhabi |
—
|
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: Abu Dhabi | Statement: [Nermal, oftenSentTo, Abu Dhabi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenSentTo Context triple: [Nermal, oftenSentTo, Abu Dhabi]
-
A.
oftenFrom
Indicates that something frequently originates, derives, or comes from a particular source or location.
-
B.
sends
chosen
Indicates that one entity transmits or dispatches something (such as a message, object, or signal) to another entity.
-
C.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
D.
sentAgainst
Indicates that something (such as a message, request, or action) is directed or dispatched in opposition to a particular target or entity.
-
E.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:07 p.m.