Triple
T14029859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads |
E337557
|
entity |
| Predicate | hasStruggleHistory |
P37550
|
FINISHED |
| Object | forced removals resistance |
—
|
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: forced removals resistance | Statement: [Crossroads, hasStruggleHistory, forced removals resistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStruggleHistory Context triple: [Crossroads, hasStruggleHistory, forced removals resistance]
-
A.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
B.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
C.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
-
D.
hasBackIssues
Indicates that an entity experiences or possesses problems, conditions, or complications related to its back.
-
E.
notableStruggles
Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.