Triple
T26817238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Condor |
E675154
|
entity |
| Predicate | typicalThemeAssociation |
P198915
|
FINISHED |
| Object | government conspiracy |
—
|
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: government conspiracy | Statement: [Condor, typicalThemeAssociation, government conspiracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalThemeAssociation Context triple: [Condor, typicalThemeAssociation, government conspiracy]
-
A.
majorThemeAssociation
Indicates that one entity is associated with another as a primary or central theme.
-
B.
primaryThemeAssociation
Indicates that one entity is the main or central theme associated with another entity.
-
C.
coreThemeAssociation
Indicates a primary, central, or defining thematic relationship between two entities, where one serves as a core theme of the other.
-
D.
associatedThemeElements
Indicates a relationship where certain elements are linked to, or grouped under, a particular theme as its related components.
-
E.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: April 27, 2026, 4:52 a.m.