Triple
T27691769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series I |
E698178
|
entity |
| Predicate | notableUsers |
P4829
|
FINISHED |
| Object | Peter Gabriel |
—
|
NE NERFINISHED |
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: Peter Gabriel | Statement: [Series I, notableUsers, Peter Gabriel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUsers Context triple: [Series I, notableUsers, Peter Gabriel]
-
A.
notableUser
chosen
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
B.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
C.
notableUserGroup
Indicates that the subject is associated with a user group that is distinguished or recognized as notable in some specific context.
-
D.
notableUserInterface
Indicates that an entity has a user interface that is particularly significant, prominent, or noteworthy in some context.
-
E.
notableUserUnit
Indicates that a particular user is distinguished or recognized as notable within a given unit, group, or context.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: April 27, 2026, 2:52 p.m.