Triple
T3271122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebel Musa |
E68649
|
entity |
| Predicate | disputedIdentification |
P13304
|
FINISHED |
| Object | location of biblical Mount Sinai |
—
|
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: location of biblical Mount Sinai | Statement: [Jebel Musa, disputedIdentification, location of biblical Mount Sinai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disputedIdentification Context triple: [Jebel Musa, disputedIdentification, location of biblical Mount Sinai]
-
A.
hasDisputedIdentityWith
chosen
Indicates that two entities are associated with conflicting, uncertain, or contested identifications, such that their true or correct identities are in dispute relative to each other.
-
B.
statusDisputedBy
Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
-
C.
disputeKnownAs
Indicates that a particular dispute is also referred to by an alternative name or title.
-
D.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
E.
hasIdentityDocument
Indicates that an entity possesses or is associated with a specific identity document.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff4b9dc8190b7e3da0bbffccf99 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.