Triple
T8035806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal IV |
E187103
|
entity |
| Predicate | producer |
P490
|
FINISHED |
| Object | Seal |
E35256
|
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: Seal | Statement: [Seal IV, producer, Seal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seal Context triple: [Seal IV, producer, Seal]
-
A.
Seal
chosen
Seal is a British singer-songwriter known for his soulful voice and hit songs such as "Kiss from a Rose."
-
B.
Seal
Seal is a village in the Sevenoaks district of Kent, England, known for its historic parish church and traditional rural character.
-
C.
Seals
Seals is the nickname of the historic San Francisco Seals baseball team, a prominent minor league club that played in the Pacific Coast League.
-
D.
Bond
Bond is a survivor perk in Dead by Daylight that allows players to see the auras of nearby teammates, enhancing coordination and support.
-
E.
Bond
Bond is a common English surname historically associated with occupational or status-based origins and borne by numerous notable figures across politics, arts, and popular culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ef68c6081908727d17238b3522a |
completed | March 31, 2026, 3:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd37b54881908c67d5746f9ef39e |
completed | April 3, 2026, 5:47 p.m. |
Created at: March 30, 2026, 5:22 p.m.