Triple
T11546931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Bird |
E273796
|
entity |
| Predicate | liveVersionLength |
P33220
|
FINISHED |
| Object | 14:10 |
—
|
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: 14:10 | Statement: [Free Bird, liveVersionLength, 14:10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveVersionLength Context triple: [Free Bird, liveVersionLength, 14:10]
-
A.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
B.
longVersionLength
chosen
Indicates that one entity specifies the length or duration of a more detailed or extended version of another entity.
-
C.
singleVersionLength
Indicates the length or duration associated with a single version of something (e.g., an item, product, or media instance).
-
D.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
E.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.