Triple
T26584577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birdie |
E667172
|
entity |
| Predicate | describesEventsOf |
P13178
|
FINISHED |
| Object | Tillerman family |
—
|
NE NERFINISHED |
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: Tillerman family | Statement: [Birdie, describesEventsOf, Tillerman family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesEventsOf Context triple: [Birdie, describesEventsOf, Tillerman family]
-
A.
eventDescription
chosen
Indicates that a textual summary or explanation is provided describing what happens in the event.
-
B.
basedOnEventsDescribedIn
Indicates that something is derived from, inspired by, or constructed using the events described in another source.
-
C.
featuresEventsFor
Indicates that something presents, highlights, or includes specific events as part of its content or offering.
-
D.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
-
E.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 2:05 a.m.