Triple
T30562480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucharest Court of Appeal |
E777882
|
entity |
| Predicate | capitalCityCourt |
P159739
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bucharest Court of Appeal, capitalCityCourt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityCourt Context triple: [Bucharest Court of Appeal, capitalCityCourt, true]
-
A.
capitalCityOfCourt
Indicates that a city serves as the official seat or capital location of a particular court.
-
B.
capitalCityCourtOf
chosen
Indicates that one entity is the main judicial court located in and serving as the primary court of the capital city of another entity.
-
C.
capitalCityOfJurisdiction
Indicates that one entity is the primary city serving as the official capital of the specified jurisdiction or governing region.
-
D.
jurisdictionCity
Indicates that a city has legal or administrative authority over, or is the governing jurisdiction for, a given entity or matter.
-
E.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:21 p.m.