Triple
T16448818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian ducat |
E399499
|
entity |
| Predicate | valueCharacteristic |
P122832
|
FINISHED |
| Object | stable value |
—
|
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: stable value | Statement: [Venetian ducat, valueCharacteristic, stable value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueCharacteristic Context triple: [Venetian ducat, valueCharacteristic, stable value]
-
A.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
B.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
C.
productCharacteristic
Indicates that a product possesses, exhibits, or is defined by a specific characteristic or attribute.
-
D.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
-
E.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32cdee44c8190ae0df20c58ff7558 |
completed | April 18, 2026, 7:03 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.