Triple
T29278975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Congress 1900 |
E742317
|
entity |
| Predicate | hasAttendeeGroup |
P167410
|
FINISHED |
| Object | European socialist parties |
—
|
NE NERFINISHED |
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: European socialist parties | Statement: [Paris Congress 1900, hasAttendeeGroup, European socialist parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttendeeGroup Context triple: [Paris Congress 1900, hasAttendeeGroup, European socialist parties]
-
A.
hasGroupMember
Indicates that a group or collection includes a specific entity as one of its members.
-
B.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
C.
hasAttendanceType
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
D.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
E.
hasAttended
Indicates that an entity has been present at or participated in a particular event, place, or gathering.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 12:53 p.m.