Triple
T36637968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECRIS-TCN |
E904510
|
entity |
| Predicate | hasCentralSystem |
P192527
|
FINISHED |
| Object | ECRIS-TCN central database |
—
|
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: ECRIS-TCN central database | Statement: [ECRIS-TCN, hasCentralSystem, ECRIS-TCN central database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralSystem Context triple: [ECRIS-TCN, hasCentralSystem, ECRIS-TCN central database]
-
A.
hasCentralOrgan
Indicates that an entity possesses a primary or main organ that serves as a central functional or structural component.
-
B.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
C.
hasCentralPlanetType
Indicates that an entity has a central planet whose type or classification is specified by the related value.
-
D.
hasCentralRegion
Indicates that an entity possesses or is associated with a primary or central area within its overall structure or domain.
-
E.
hasCentralStar
Indicates that an astronomical system or structure possesses a primary star located at its center.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: May 3, 2026, 4:11 p.m.