Triple
T24107077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queue |
E597254
|
entity |
| Predicate | hasNotableEntrepreneurInvolved |
P155089
|
FINISHED |
| Object | Spencer Rascoff |
—
|
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: Spencer Rascoff | Statement: [Queue, hasNotableEntrepreneurInvolved, Spencer Rascoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEntrepreneurInvolved Context triple: [Queue, hasNotableEntrepreneurInvolved, Spencer Rascoff]
-
A.
hasNotableFounder
Indicates that an entity was founded or established by a person or organization considered especially significant or noteworthy.
-
B.
coFounderNotableFor
Indicates that a person is a co-founder of something for which they are notably recognized.
-
C.
notableCEO
Indicates that the subject is a chief executive officer who is widely recognized or distinguished in a notable way.
-
D.
hasNotableCompany
Indicates that an entity is associated with or linked to a company that is considered notable or significant in some context.
-
E.
notableCoFounderOccupation
Indicates that the co-founder is particularly notable or recognized for having a specific occupation.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de17e650819085ae522e00aa82f3 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:01 p.m.