Triple
T32249245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fly By II |
E823836
|
entity |
| Predicate | hasReworkedVersionOf |
P15288
|
FINISHED |
| Object | Fly By |
E823836
|
NE 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: Fly By | Statement: [Fly By II, hasReworkedVersionOf, Fly By]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReworkedVersionOf Context triple: [Fly By II, hasReworkedVersionOf, Fly By]
-
A.
reworkedBy
Indicates that an existing work, product, or result has been modified, revised, or substantially altered by a particular agent.
-
B.
isReprofiledVersionOf
Indicates that one entity is a modified or updated version of another, created by changing its profile, configuration, or characteristics while retaining its core identity or origin.
-
C.
isVersionOf
chosen
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
D.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
E.
hasRevisedOrigin
Indicates that the origin of an entity has been updated or modified from its previous or initial state.
- F. None of above.
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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01f4d954e08190aff3756955212d67 |
completed | May 11, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34703607848190b0d4df8c70b86368 |
completed | June 18, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_6a01edadb9248190be592287530740a5 |
completed | May 11, 2026, 2:54 p.m. |
Created at: May 1, 2026, 12:40 a.m.