Triple
T26847404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qom (Toba) |
E675961
|
entity |
| Predicate | hasStruggleFor |
P3839
|
FINISHED |
| Object | land rights |
—
|
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: land rights | Statement: [Qom (Toba), hasStruggleFor, land rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStruggleFor Context triple: [Qom (Toba), hasStruggleFor, land rights]
-
A.
struggleFor
chosen
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
B.
associatedWithStruggle
Indicates a relationship in which an entity is connected to, involved in, or characterized by a particular struggle, conflict, or hardship.
-
C.
notableStruggles
Indicates that the subject has faced significant challenges, difficulties, or adversities that are especially noteworthy or defining.
-
D.
meansOfStruggle
Indicates the method, tactic, or form of action used by an entity in carrying out a struggle or conflict.
-
E.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 27, 2026, 5:13 a.m.