Triple
T19238569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philistine bichrome pottery |
E481066
|
entity |
| Predicate | hasVesselForm |
P108469
|
FINISHED |
| Object | krater |
—
|
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: krater | Statement: [Philistine bichrome pottery, hasVesselForm, krater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVesselForm Context triple: [Philistine bichrome pottery, hasVesselForm, krater]
-
A.
hasVessel
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
B.
vesselForm
chosen
Indicates that one entity has the physical shape, structure, or configuration of a vessel or container.
-
C.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
D.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
E.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faef827c81909157bbcd4060dfc9 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.