Triple
T18635750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERC Open |
E455541
|
entity |
| Predicate | relationToOtherClasses |
P127424
|
FINISHED |
| Object | runs alongside main ERC categories |
—
|
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: runs alongside main ERC categories | Statement: [ERC Open, relationToOtherClasses, runs alongside main ERC categories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToOtherClasses Context triple: [ERC Open, relationToOtherClasses, runs alongside main ERC categories]
-
A.
relationToTraceClass
Indicates that one entity stands in a specified relationship to a particular trace class, such as being derived from, associated with, or belonging to that trace classification.
-
B.
relatedClassification
chosen
Indicates a relationship where one classification is associated with, linked to, or otherwise contextually connected to another classification.
-
C.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
- 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.