Triple
T18170185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Philhellenic Committee |
E435002
|
entity |
| Predicate | supportedPeople |
P130735
|
FINISHED |
| Object | Greek revolutionaries |
—
|
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 revolutionaries | Statement: [Swiss Philhellenic Committee, supportedPeople, Greek revolutionaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedPeople Context triple: [Swiss Philhellenic Committee, supportedPeople, Greek revolutionaries]
-
A.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
B.
personalUnionResult
Indicates that a personal union between entities has occurred and specifies the resulting combined political or dynastic arrangement.
-
C.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
-
D.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
E.
supportsPhoneBook
Indicates that an entity provides functionality for managing or accessing a phone book or contact list.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df555af081908a2f12bce6a13f56 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:30 a.m.