Triple
T6122666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbird |
E136519
|
entity |
| Predicate | supportsCalendar |
P1818
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thunderbird, supportsCalendar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCalendar Context triple: [Thunderbird, supportsCalendar, true]
-
A.
usesCalendar
chosen
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
B.
supportsEventSeries
Indicates that an entity provides the necessary functionality or resources to host, manage, or accommodate a recurring series of related events.
-
C.
supportedEvent
Indicates that an entity is capable of recognizing, handling, or being associated with a particular type of event.
-
D.
hasCalendarCustom
Indicates that an entity is associated with a customized or non-default calendar configuration or behavior.
-
E.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c247b7081909972b40afb165e6f |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.