Triple
T20321991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Syrian Army |
E492226
|
entity |
| Predicate | hasSplinterGroup |
P137970
|
FINISHED |
| Object | Islamist rebel factions |
—
|
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: Islamist rebel factions | Statement: [Free Syrian Army, hasSplinterGroup, Islamist rebel factions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSplinterGroup Context triple: [Free Syrian Army, hasSplinterGroup, Islamist rebel factions]
-
A.
hasSplitOffGroups
chosen
Indicates that an entity has given rise to one or more groups that have separated from it to form distinct subgroups or offshoots.
-
B.
hasRepresentativeGroup
Indicates that an entity is associated with, or formally represented by, a specific group acting on its behalf.
-
C.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
D.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
E.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778c4430819083b17da5067b88ef |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.