Triple
T33503732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | #ViaCatalana |
E858060
|
entity |
| Predicate | eventTypeDiscussed |
P119424
|
FINISHED |
| Object | human chain |
—
|
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: human chain | Statement: [#ViaCatalana, eventTypeDiscussed, human chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeDiscussed Context triple: [#ViaCatalana, eventTypeDiscussed, human chain]
-
A.
typeOfEvent
Indicates that one entity is classified as a specific kind or category of event.
-
B.
genreOfDescribedEvents
chosen
Indicates that one entity specifies the genre or type category of the events described by another entity.
-
C.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
D.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
E.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:38 a.m.