Triple
T19702586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCD |
E473131
|
entity |
| Predicate | legalStatusAfter2011 |
P136998
|
FINISHED |
| Object | dissolved |
—
|
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: dissolved | Statement: [RCD, legalStatusAfter2011, dissolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfter2011 Context triple: [RCD, legalStatusAfter2011, dissolved]
-
A.
legalStatusAfter2013
Indicates the legal status or condition of an entity as it applies from the year 2013 onward.
-
B.
legalStatusAfter2009
Indicates the legal status or condition that an entity holds from the year 2009 onward, typically reflecting changes due to laws or regulations taking effect at or after that time.
-
C.
legalStatusAfter2005
Indicates the legal status or condition that applies to an entity starting from the year 2005 onward.
-
D.
legalStatusAfter1991
Indicates the legal status or condition that an entity holds from the year 1991 onward, typically reflecting changes due to laws or regulations enacted at or after that time.
-
E.
legalStatusAfter2018
Indicates the legal status or condition that an entity holds starting from the year 2018 onward.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b758348190b0cf58d6b2f13e7f |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.