Triple
T32016002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mob Song |
E817540
|
entity |
| Predicate | sequenceSetting |
P173494
|
FINISHED |
| Object | French provincial town |
—
|
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: French provincial town | Statement: [The Mob Song, sequenceSetting, French provincial town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceSetting Context triple: [The Mob Song, sequenceSetting, French provincial town]
-
A.
sequenceDirector
Indicates that one entity serves as the director responsible for overseeing or managing a particular sequence associated with another entity.
-
B.
sequenceNotation
Indicates that one entity specifies the ordered symbolic representation (notation) used to express a sequence associated with another entity.
-
C.
sequenceID
Indicates that an entity is associated with a specific position or identifier within an ordered sequence.
-
D.
sequenceBegins
Indicates that one sequence starts at the beginning of, or is the initial part of, another sequence.
-
E.
sequenceWith
Indicates that one entity occurs in a specific order directly before or after another entity as part of a defined sequence.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:16 a.m.