Triple
T27065502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sanctuary |
E685161
|
entity |
| Predicate | alliedAgainstBy |
P162043
|
FINISHED |
| Object | Alexandria Safe-Zone |
—
|
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: Alexandria Safe-Zone | Statement: [The Sanctuary, alliedAgainstBy, Alexandria Safe-Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alliedAgainstBy Context triple: [The Sanctuary, alliedAgainstBy, Alexandria Safe-Zone]
-
A.
alliedAgainstBy
chosen
Indicates that the subject is opposed by an entity that has formed an alliance with others against it.
-
B.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
C.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with another entity.
-
D.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
E.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:24 a.m.