Triple
T36472574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time for Me to Fly |
E898573
|
entity |
| Predicate | hasEnduringRadioPresence |
P169918
|
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: [Time for Me to Fly, hasEnduringRadioPresence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnduringRadioPresence Context triple: [Time for Me to Fly, hasEnduringRadioPresence, true]
-
A.
hasRadioPresence
chosen
Indicates that an entity maintains a detectable or active presence in radio broadcasts or radio communication channels.
-
B.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
C.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
D.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
E.
hasExternalAntenna
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:10 p.m.