Triple
T35471009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independents |
E1025206
|
entity |
| Predicate | perceptionByAlliance |
P183786
|
FINISHED |
| Object | separatists |
—
|
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: separatists | Statement: [Independents, perceptionByAlliance, separatists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionByAlliance Context triple: [Independents, perceptionByAlliance, separatists]
-
A.
relativeByAlliance
Indicates a familial or kinship relationship that exists due to an alliance, such as marriage or a formal pact, rather than by blood.
-
B.
recognizedAlliance
Indicates that one party formally acknowledges the existence and validity of an alliance involving another party.
-
C.
involvesAlliance
Indicates that there exists a cooperative or strategic alliance relationship between the referenced entities.
-
D.
allianceStatus
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
E.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:04 p.m.