Triple
T10791696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Muntasir |
E254593
|
entity |
| Predicate | militarySupportBase |
P1869
|
FINISHED |
| Object | Turkish guard in Samarra |
—
|
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: Turkish guard in Samarra | Statement: [al-Muntasir, militarySupportBase, Turkish guard in Samarra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militarySupportBase Context triple: [al-Muntasir, militarySupportBase, Turkish guard in Samarra]
-
A.
militaryBasis
Indicates that one entity serves as the foundational military justification, rationale, or underlying military reason for another entity or action.
-
B.
militaryBaseVenue
Indicates that an event or activity takes place at, or is hosted by, a military base as its venue.
-
C.
militaryBaseStatus
Indicates the operational condition or readiness state of a military base at a given time.
-
D.
hasMilitaryBase
chosen
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f6dfcc81909096895c588ef46f |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.