Triple
T31002861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Leuven |
E789985
|
entity |
| Predicate | modernCountryEquivalent |
P139080
|
FINISHED |
| Object | Belgium |
—
|
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: Belgium | Statement: [Count of Leuven, modernCountryEquivalent, Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCountryEquivalent Context triple: [Count of Leuven, modernCountryEquivalent, Belgium]
-
A.
modernCountryContains
Indicates that a modern country geographically encompasses, within its current internationally recognized borders, the location or territory of another entity.
-
B.
countryEquivalent
chosen
Indicates that two country entities are considered equivalent or represent the same country in the given context.
-
C.
modernCountryClaim
Indicates that a modern country asserts sovereignty, ownership, or official association with a given entity or territory.
-
D.
modernCountryDuringEvent
Indicates that a modern country existed or was relevant as a political entity during the time span of a specified historical event.
-
E.
formerlyCountry
Indicates that an entity was previously recognized as a country but no longer holds that status.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 8:57 p.m.