Triple
T31639796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segestes |
E807413
|
entity |
| Predicate | laterDeliveredTo |
P199784
|
FINISHED |
| Object | Roman protection |
—
|
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: Roman protection | Statement: [Segestes, laterDeliveredTo, Roman protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDeliveredTo Context triple: [Segestes, laterDeliveredTo, Roman protection]
-
A.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
B.
deliveredToOperator
Indicates that something (such as a message, item, or signal) has been successfully delivered to an operator as the recipient.
-
C.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
D.
deliveredWith
Indicates that one item, service, or message is brought or transported to a recipient together with another, as part of the same delivery.
-
E.
deliveredByLaterRegardedAs
Indicates that something was delivered by an entity that was later regarded or recognized in a particular way.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
| PDg | Predicate description generation | batch_69ff58031bb081909fea985b16f69da4 |
completed | May 9, 2026, 3:51 p.m. |
Created at: April 30, 2026, 10:49 p.m.