Triple
T30292129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C.R. |
E770406
|
entity |
| Predicate | orderCityOfOrigin |
P175263
|
FINISHED |
| Object | Rome |
—
|
NE NERFINISHED |
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: Rome | Statement: [C.R., orderCityOfOrigin, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderCityOfOrigin Context triple: [C.R., orderCityOfOrigin, Rome]
-
A.
orderCountryOfOrigin
Indicates the country from which an order was originally placed, sourced, or shipped.
-
B.
cargoOrigin
Indicates that a specified location is the starting point from which the cargo was initially shipped or dispatched.
-
C.
portOfOrigin
Indicates the location from which something (such as a shipment or vessel) originally departs or is first sent.
-
D.
orderFoundedIn
Indicates the place or location where an order (such as a religious, military, or organizational order) was originally established or founded.
-
E.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 7:47 p.m.