Triple
T29600347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eger |
E754423
|
entity |
| Predicate | coordinateSubject |
P171278
|
FINISHED |
| Object | Cheb |
—
|
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: Cheb | Statement: [Eger, coordinateSubject, Cheb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateSubject Context triple: [Eger, coordinateSubject, Cheb]
-
A.
subjectKey
Indicates that the subject serves as a unique key or identifier used to reference or distinguish an entity in a relationship or dataset.
-
B.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
C.
coordinateNote
Indicates that one note is coordinated with another, typically aligning or synchronizing their positions or roles within a shared structure or context.
-
D.
coordinateRoleIn
Indicates a relationship where one entity organizes, aligns, or manages the roles or responsibilities of another entity within a shared activity, structure, or context.
-
E.
subjectMovement
Indicates that the subject changes its position or location, capturing the action or process of moving.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 28, 2026, 6:21 p.m.