Triple
T12413764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton Pierrots |
E296582
|
entity |
| Predicate | has background |
P15585
|
FINISHED |
| Object | dark, indistinct seafront |
—
|
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: dark, indistinct seafront | Statement: [Brighton Pierrots, has background, dark, indistinct seafront]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has background Context triple: [Brighton Pierrots, has background, dark, indistinct seafront]
-
A.
hasBackground
chosen
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
B.
hasAuthorBackgroundIn
Indicates that an author possesses a particular background, such as education, experience, or expertise, in a specified field or domain.
-
C.
hasNotableHostBackground
Indicates that the host of an event, show, or program has a background or profile that is considered particularly significant, distinguished, or noteworthy.
-
D.
hasMemberBackground
Indicates that an entity has information describing the background or history of one of its members.
-
E.
hasBackTo
Indicates that one entity is positioned or oriented with its back facing toward another entity.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.