Triple
T13785418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Balad |
E331242
|
entity |
| Predicate | hasOpeningOath |
P43456
|
FINISHED |
| Object | By this city (Mecca) |
—
|
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: By this city (Mecca) | Statement: [Al-Balad, hasOpeningOath, By this city (Mecca)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningOath Context triple: [Al-Balad, hasOpeningOath, By this city (Mecca)]
-
A.
hasOpeningOathBy
chosen
Indicates that something (such as a document, speech, or text) begins with an oath delivered or authored by a particular entity.
-
B.
hasOpeningOathStyle
Indicates that an entity’s opening oath is expressed in a particular stylistic form or manner.
-
C.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
D.
administersOathTo
Indicates that one entity formally gives or conducts an oath that another entity takes.
-
E.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.