Triple
T18102543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solomos |
E433257
|
entity |
| Predicate | advocacyFor |
P33
|
FINISHED |
| Object | Greek independence |
—
|
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: Greek independence | Statement: [Solomos, advocacyFor, Greek independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocacyFor Context triple: [Solomos, advocacyFor, Greek independence]
-
A.
advocatesAgainst
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
B.
advocacyMovement
Indicates that an entity actively supports, promotes, or works to advance a particular social, political, or ideological movement.
-
C.
advocates
chosen
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
D.
advocacyOrganization
Indicates that an organization actively supports, promotes, or works on behalf of a cause, issue, or group through advocacy activities.
-
E.
hasAdvocacyMethod
Indicates the method, strategy, or approach used to advocate for a cause, issue, or entity.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb7be948190b4ed4586f731d6f2 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.