Triple
T12804498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Inshiqaq |
E306107
|
entity |
| Predicate | hasMainAddressee |
P92617
|
FINISHED |
| Object | human being as accountable before God |
—
|
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: human being as accountable before God | Statement: [Al-Inshiqaq, hasMainAddressee, human being as accountable before God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAddressee Context triple: [Al-Inshiqaq, hasMainAddressee, human being as accountable before God]
-
A.
addresseeOf
chosen
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
B.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
C.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
D.
normAddressee
Indicates that a particular entity is the socially or conventionally appropriate recipient or target of an utterance, message, or communicative act.
-
E.
hasPostalAddressComponent
Indicates that an entity is associated with a specific part or element of a postal address (such as street, city, or postal code).
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7e3be48190ba9159c9f1ac2ccd |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.