Triple
T35805308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Brand Extension 2002 |
E1035087
|
entity |
| Predicate | createdSeparateRosterFor |
P152185
|
FINISHED |
| Object | Raw |
—
|
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: Raw | Statement: [WWE Brand Extension 2002, createdSeparateRosterFor, Raw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdSeparateRosterFor Context triple: [WWE Brand Extension 2002, createdSeparateRosterFor, Raw]
-
A.
hasExpandedRoster
Indicates that an entity’s roster, lineup, or membership has increased in size compared to a previous state.
-
B.
hasRostersFor
chosen
Indicates that an entity maintains or provides one or more rosters associated with another entity, context, or time period.
-
C.
supportsSeparateAccounts
Indicates that one entity enables or allows the use or management of distinct, individually maintained accounts rather than a single shared account.
-
D.
rosterControl
Indicates a relationship where one entity manages, configures, or oversees the composition and changes of a group or roster of other entities.
-
E.
createdBySeparationFrom
Indicates that one entity comes into existence as a result of being separated or split off from 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:06 p.m.