Triple
T25475243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanem |
E638412
|
entity |
| Predicate | addressFormPosition |
P4477
|
FINISHED |
| Object | follows personal name |
—
|
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: follows personal name | Statement: [Hanem, addressFormPosition, follows personal name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressFormPosition Context triple: [Hanem, addressFormPosition, follows personal name]
-
A.
addressFormFor
chosen
Indicates the form of address or mode of speaking that one entity should use when referring to or speaking to another entity.
-
B.
addressesPosition
Indicates that one entity communicates with, responds to, or deals with the role, status, or job position held by another entity.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f754447c8190acc16c440f8bb03d |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:25 p.m.