Triple
T5024375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah |
E112936
|
entity |
| Predicate | visits |
P60586
|
FINISHED |
| Object | Samuel annually |
—
|
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: Samuel annually | Statement: [Hannah, visits, Samuel annually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visits Context triple: [Hannah, visits, Samuel annually]
-
A.
visitedDuring
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
B.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
C.
notableVisit
Indicates that one entity made a visit to another entity or location that is considered significant or noteworthy.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736852e88190b69d6561ca7604c3 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd724ff2b4819091351cf80d3647a1 |
completed | March 20, 2026, 4:14 p.m. |
Created at: March 20, 2026, 1:36 p.m.