Triple
T35846834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How We Roll (with Big Pun) |
E1036235
|
entity |
| Predicate | earlySingleOf |
P28436
|
FINISHED |
| Object | Ashanti |
—
|
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: Ashanti | Statement: [How We Roll (with Big Pun), earlySingleOf, Ashanti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlySingleOf Context triple: [How We Roll (with Big Pun), earlySingleOf, Ashanti]
-
A.
singleFrom
chosen
Indicates that one entity is derived as a single, distinct item from another source or collection.
-
B.
singleWith
Indicates that an entity is unmarried and not currently in a romantic relationship.
-
C.
singleBy
Indicates that an entity is not in a romantic relationship and is considered single according to a specified criterion or context.
-
D.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
E.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.