Triple
T38554660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château du Girsberg |
E925210
|
entity |
| Predicate | neighboringCastle |
P45134
|
FINISHED |
| Object | Château de Saint-Ulrich |
—
|
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: Château de Saint-Ulrich | Statement: [Château du Girsberg, neighboringCastle, Château de Saint-Ulrich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringCastle Context triple: [Château du Girsberg, neighboringCastle, Château de Saint-Ulrich]
-
A.
nearbyCastle
chosen
Indicates that one entity is located close to or within a short distance of a castle.
-
B.
nearbyCastleFunction
Indicates that one entity serves as a functional or operational counterpart (such as support, service, or utility) for a castle located nearby another entity.
-
C.
eraOfMainCastle
Indicates the historical period or era during which the main castle associated with an entity was built, used, or most prominent.
-
D.
castleName
Indicates that an entity has the specified name of a castle.
-
E.
hasCastle
Indicates that one entity possesses, controls, or contains a castle.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.