Triple
T32006245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dertosa |
E817274
|
entity |
| Predicate | autonomousCommunityToday |
P99815
|
FINISHED |
| Object | Catalonia |
—
|
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: Catalonia | Statement: [Dertosa, autonomousCommunityToday, Catalonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousCommunityToday Context triple: [Dertosa, autonomousCommunityToday, Catalonia]
-
A.
autonomousCommunity
Indicates that one entity is an autonomous community (a self-governing territorial division) within the jurisdiction or structure of another entity.
-
B.
inAutonomousCommunity
chosen
Indicates that one entity is located within or belongs administratively to a specific autonomous community.
-
C.
autonomousCommunityStatusSince
Indicates the point in time since which an entity has held the status of an autonomous community.
-
D.
presentDayMunicipality
Indicates that one entity is the current-day municipality encompassing or corresponding to the area or jurisdiction of another (typically historical) entity.
-
E.
autonomousCommunityCapital
Indicates that a city serves as the capital of a specific autonomous community or region within a country.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b40069088190b352c80db1417268 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:15 a.m.