Triple
T5922905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joyent |
E131738
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | TextDrive |
E554838
|
NE 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: TextDrive | Statement: [Joyent, formerName, TextDrive]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TextDrive Context triple: [Joyent, formerName, TextDrive]
-
A.
TextDrive
chosen
TextDrive was an early web hosting and application deployment company known for serving developers and open-source projects, which later evolved into what became Joyent.
-
B.
inDrive
inDrive is a global ride-hailing and mobility platform known for its unique model that lets passengers and drivers negotiate fares directly through the app.
-
C.
Zoho WorkDrive
Zoho WorkDrive is a cloud-based file storage, collaboration, and team content management platform offered by Zoho.
-
D.
Adobe Document Cloud
Adobe Document Cloud is Adobe’s integrated suite of cloud-based services and apps for creating, editing, managing, and securely sharing PDF documents across devices.
-
E.
Google Drive
Google Drive is a cloud-based file storage and synchronization service by Google that lets users store, share, and access files from any internet-connected device.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03804d9808190829a418adb7864aa |
completed | March 22, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e39ea48c8190a968f81f0e26ccbf |
completed | March 23, 2026, 6:54 a.m. |
Created at: March 22, 2026, 4 p.m.