Triple
T23573770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronzes of Riace |
E580188
|
entity |
| Predicate | transportPurpose |
P153226
|
FINISHED |
| Object | restoration and study |
—
|
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: restoration and study | Statement: [Bronzes of Riace, transportPurpose, restoration and study]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportPurpose Context triple: [Bronzes of Riace, transportPurpose, restoration and study]
-
A.
journeyPurpose
Indicates the reason or intended goal motivating an entity’s journey or trip.
-
B.
routePurpose
Indicates the intended function or goal that a particular route is designed or used to serve.
-
C.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
D.
bookingPurpose
Indicates the reason or intended use for which a booking or reservation is made.
-
E.
flightPurpose
Indicates the reason or intended purpose for which a particular flight is being taken or operated.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:37 p.m.