Triple
T4757567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latinus |
E105624
|
entity |
| Predicate | offersInMarriage |
P53943
|
FINISHED |
| Object | Lavinia to Aeneas |
—
|
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: Lavinia to Aeneas | Statement: [Latinus, offersInMarriage, Lavinia to Aeneas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersInMarriage Context triple: [Latinus, offersInMarriage, Lavinia to Aeneas]
-
A.
arrangedMarriageFor
chosen
Indicates that one entity has organized or set up a marriage for another entity.
-
B.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
-
C.
offersProduct
Indicates that one entity makes a product available to another entity, typically for sale or use.
-
D.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
-
E.
marriageContext
Indicates the situational or cultural circumstances under which a marriage occurs or exists, such as legal, social, or religious conditions surrounding the marital relationship.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64ec16a0819089836e4388b555f6 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.