Triple
T7970461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WEB SLINGERS: A Spider-Man Adventure |
E185308
|
entity |
| Predicate | guestRole |
P80078
|
FINISHED |
| Object | WEB recruits |
—
|
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: WEB recruits | Statement: [WEB SLINGERS: A Spider-Man Adventure, guestRole, WEB recruits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestRole Context triple: [WEB SLINGERS: A Spider-Man Adventure, guestRole, WEB recruits]
-
A.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
B.
gammaRole
Indicates a tertiary or supporting role that an entity plays within a structured hierarchy of roles or participants in an event or relationship.
-
C.
guestFlow
Indicates the movement or progression of guests through a space, process, or experience over time.
-
D.
siteRole
Indicates the specific function, responsibility, or position an entity holds within a particular site or location.
-
E.
visitorProfile
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd304dc8190b9feee5e17fc66db |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:13 p.m.