Triple
T32063852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warby Parker |
E818819
|
entity |
| Predicate | wentPublicMethod |
P173175
|
FINISHED |
| Object | direct listing |
—
|
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: direct listing | Statement: [Warby Parker, wentPublicMethod, direct listing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wentPublicMethod Context triple: [Warby Parker, wentPublicMethod, direct listing]
-
A.
wentPrivateIn
Indicates that an entity transitioned from public to private status at or during the specified time or event.
-
B.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
C.
wentPublicInDecade
Indicates that an entity became a publicly traded company during a specified decade.
-
D.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
E.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f85ea881908ce0bbddd9426e73 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:22 a.m.