Triple
T29320741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabataeans |
E743506
|
entity |
| Predicate | annexedAs |
P166838
|
FINISHED |
| Object | Roman province of Arabia Petraea |
—
|
NE NERFINISHED |
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: Roman province of Arabia Petraea | Statement: [Nabataeans, annexedAs, Roman province of Arabia Petraea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexedAs Context triple: [Nabataeans, annexedAs, Roman province of Arabia Petraea]
-
A.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
B.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
C.
annexedTerritory
Indicates that one political entity has formally incorporated another territory into its own sovereign domain.
-
D.
annexationBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity, typically through formal or forceful territorial expansion.
-
E.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665efcf4081909f6bda56798318c6 |
completed | May 2, 2026, 9 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661e9cb308190a56e25dc17df248e |
completed | May 2, 2026, 8:43 p.m. |
Created at: April 28, 2026, 1:23 p.m.