Triple
T18635669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERC Junior |
E455538
|
entity |
| Predicate | categoryRole |
P102097
|
FINISHED |
| Object | support series |
—
|
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: support series | Statement: [ERC Junior, categoryRole, support series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryRole Context triple: [ERC Junior, categoryRole, support series]
-
A.
catalogRole
Indicates that an entity holds a specific functional role or responsibility within the context of a catalog or cataloging system.
-
B.
themeRole
Indicates that an entity is the primary participant undergoing or affected by the action or event expressed by a predicate.
-
C.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
D.
classificationRole
chosen
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
E.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc80b308190932303231524d372 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.