Triple
T4683088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. McFeely |
E103849
|
entity |
| Predicate | oftenArrivesBy |
P58994
|
FINISHED |
| Object | bicycle |
—
|
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: bicycle | Statement: [Mr. McFeely, oftenArrivesBy, bicycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenArrivesBy Context triple: [Mr. McFeely, oftenArrivesBy, bicycle]
-
A.
mustBeDeliveredBy
Indicates that one entity is required to be delivered or completed no later than a specified time, date, or deadline set by another entity.
-
B.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
C.
peakDeliveryTime
Indicates the time period during which deliveries are expected to be at their highest volume or frequency.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:16 p.m.