Triple
T24870610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Sebastian |
E622412
|
entity |
| Predicate | creativeStatus |
P158129
|
FINISHED |
| Object | fictional location |
—
|
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: fictional location | Statement: [Port Sebastian, creativeStatus, fictional location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeStatus Context triple: [Port Sebastian, creativeStatus, fictional location]
-
A.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
B.
hasCreativeWorkStatus
Indicates the current state or condition of a creative work within its lifecycle (e.g., planned, in progress, completed, or published).
-
C.
creativeOutput
Indicates that an entity produces, originates, or is responsible for a creative work or result.
-
D.
creativeScope
Indicates the range or domain within which an entity is allowed or intended to exercise creativity or generate original content.
-
E.
creativeContributor
Indicates a relationship where an entity plays an active role in originating, designing, or shaping the creative content or form of another entity.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 18, 2026, 5:23 a.m.