Triple
T7904507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Dan Taylor |
E183537
|
entity |
| Predicate | appearsAtEvent |
P149
|
FINISHED |
| Object | Forrest and Jenny’s wedding |
—
|
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: Forrest and Jenny’s wedding | Statement: [Lieutenant Dan Taylor, appearsAtEvent, Forrest and Jenny’s wedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAtEvent Context triple: [Lieutenant Dan Taylor, appearsAtEvent, Forrest and Jenny’s wedding]
-
A.
presentsAt
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
-
B.
participatedInEvent
chosen
Indicates that an entity took part in or was actively involved in a specific event.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
-
E.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a4331cc8190b50301c78767a850 |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.