Triple
T35807744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edge-O-Matic |
E1035144
|
entity |
| Predicate | notableUserRealName |
—
|
GENERATED |
| Object | Adam Copeland |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUserRealName Context triple: [Edge-O-Matic, notableUserRealName, Adam Copeland]
-
A.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
B.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
C.
notableUserAlias
Indicates that a user is known or recognized by a particular alternate name or alias.
-
D.
notableMemberCommonName
Indicates that the object is the commonly used or well-known name of a notable member associated with the subject.
-
E.
usedByRealName
Indicates that something (such as an alias, handle, or resource) is used by an entity identified by their real, legal name.
- F. None of above.
Provenance (1 batch)
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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.