Triple
T37767224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trauntal |
E941446
|
entity |
| Predicate | isCarvedBy |
P189017
|
FINISHED |
| Object | Traun River |
E276375
|
NE 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: Traun River | Statement: [Trauntal, isCarvedBy, Traun River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCarvedBy Context triple: [Trauntal, isCarvedBy, Traun River]
-
A.
isCarvedWith
Indicates that one entity has been shaped, decorated, or formed by carving using another entity as the tool, method, or material.
-
B.
carvedBy
Indicates that one entity has been shaped, cut, or sculpted from a material by another entity through a carving process.
-
C.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
D.
carvedOutOf
Indicates that one entity has been physically shaped, cut, or formed from the material of another entity.
-
E.
carvedInto
Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
- F. None of above. chosen
Provenance (5 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167f39cd8819093758c409b7d5518 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.