Triple
T14848042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bounty (1983 film replica ship) |
E349152
|
entity |
| Predicate | hasFunctionAfterFilming |
P115862
|
FINISHED |
| Object | sailing attraction |
—
|
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: sailing attraction | Statement: [Bounty (1983 film replica ship), hasFunctionAfterFilming, sailing attraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionAfterFilming Context triple: [Bounty (1983 film replica ship), hasFunctionAfterFilming, sailing attraction]
-
A.
hasAfterMovie
Indicates that one movie or media work occurs or is intended to be watched immediately after another as a follow-up or subsequent viewing.
-
B.
hasLiveActionFilm
Indicates that a subject has a corresponding live-action film adaptation or representation.
-
C.
filmicFunction
Indicates the role or purpose that something serves within the structure, style, or narrative function of a film.
-
D.
hasFilmExperience
Indicates that an entity has prior involvement or participation in film-related activities or productions.
-
E.
endedWithFilm
Indicates that an event, series, or process concluded with the showing, release, or occurrence of a particular film.
- F. None of above. chosen
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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded29236dc8190b7d3a37d09f9fb21 |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:53 a.m.