Triple
T15962164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Monastery |
E387087
|
entity |
| Predicate | inscriptionPresence |
P120624
|
FINISHED |
| Object | Nabataean inscriptions nearby |
—
|
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: Nabataean inscriptions nearby | Statement: [The Monastery, inscriptionPresence, Nabataean inscriptions nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionPresence Context triple: [The Monastery, inscriptionPresence, Nabataean inscriptions nearby]
-
A.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
B.
inscriptionList
Indicates that there is a list or collection of inscriptions associated with an entity.
-
C.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
D.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
-
E.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
- F. None of above. chosen
Provenance (4 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e173af801c8190bfc0f602831bb594 |
completed | April 16, 2026, 11:41 p.m. |
Created at: April 10, 2026, 4:53 a.m.