Triple
T21516630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kataeb Party |
E530858
|
entity |
| Predicate | notableStance |
P109408
|
FINISHED |
| Object | anti-communism |
—
|
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: anti-communism | Statement: [Kataeb Party, notableStance, anti-communism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStance Context triple: [Kataeb Party, notableStance, anti-communism]
-
A.
notableStand
chosen
Indicates that an entity is particularly well-known or distinguished for a specific stance, position, or viewpoint.
-
B.
notableState
Indicates that an entity is significantly associated with, recognized in, or prominently linked to a particular state (such as a U.S. state or similar regional jurisdiction).
-
C.
notableOpinion
Indicates that one entity holds a significant or widely recognized opinion or viewpoint about another entity.
-
D.
notableArgument
Indicates that an entity plays a particularly important, prominent, or distinguished role as an argument (participant) in a given relation or event.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee814278e08190a66d516bed0726b5 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.