Triple
T6873291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold V, Duke of Austria |
E158604
|
entity |
| Predicate | captured at |
P16653
|
FINISHED |
| Object | near Vienna |
—
|
LITERAL 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: near Vienna | Statement: [Leopold V, Duke of Austria, captured at, near Vienna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captured at Context triple: [Leopold V, Duke of Austria, captured at, near Vienna]
-
A.
capturedAt
Indicates the specific time or moment at which an entity was captured, recorded, or taken.
-
B.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
C.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
-
D.
capturedIn
chosen
Indicates that one entity was taken prisoner, seized, or otherwise brought under control within the context, location, or event represented by another entity.
-
E.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c73ea08190b6bb1463e7ead47b |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.